Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add a `dapr update` command to update the CLI itself

Aperta
  • Qualcosa non va?
#1,725 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@marcduiker ci sta già lavorando.

Dal 22/10/2026.

  • #1726 di @marcduiker — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, go
Ambito
cli

Direzione di ricerca

The issue does not name implementation files or tests. Start by locating the CLI command definitions and existing install or release handling; then map the platform-specific binary replacement and checksum paths described here. Done means dapr update handles stable and specified versions, leaves package manager installs alone, verifies downloads, and reports the stated failure cases; the author says an implementation is already ready and plans a PR.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Describe the feature

Add a dapr update command that updates the Dapr CLI itself, on Linux, macOS and Windows. Today users have to look up the install script URL (or remember which package manager they used) to update the CLI. Many other CLIs provide a single self-update command.

Proposed behavior
  • dapr update updates the CLI to the latest stable release.
  • dapr update --version <version> installs a specific version (including release candidates and downgrades). A partial version like 1.18 or latest is rejected up front.
  • Package manager installs are left alone. If the CLI was installed with Homebrew or the Windows MSI/winget, the command doesn't touch the binary and prints the right command instead, for example brew upgrade dapr/tap/dapr-cli or winget upgrade Dapr.CLI (winget install Dapr.CLI.Preview --version X for RCs).
  • The latest stable version comes from https://github.com/dapr/cli/releases.atom, skipping rc tags, which is the same source install.sh uses. There's no GitHub API rate limit. releases/latest isn't used, because releases are published as pre-releases and promoted by hand, so it lags behind.
  • Downloads are verified against the published .sha256 file before anything is replaced.
  • The binary is replaced safely:
    • The new binary is written next to the current one, then moved into place with an atomic rename on Linux/macOS.
    • On Windows the running dapr.exe is renamed aside first, with a rollback if the swap fails.
    • If anything fails, the existing binary is left untouched.
  • Clear errors:
    • Offline or airgapped machines get a clear error.
    • A non-writable install directory (for example /usr/local/bin) suggests sudo dapr update or an elevated shell.
    • A version that doesn't exist gets a "not found for /" error.
Out of scope
  • No background "new version available" check, and no caching. The CLI only contacts the network when dapr update runs. This is deliberately simpler than #1059.
  • Runtime binaries are not updated. Only the CLI binary changes; nothing installed by dapr init is touched.
Related
  • #1059: proposal to check for CLI and runtime updates while other commands run
  • #1454: CLI install script release source

I have an implementation ready, with unit tests and a smoke test against the real GitHub releases, and will open a PR referencing this issue.

Release Note

RELEASE NOTE: ADD dapr update command to update the Dapr CLI to the latest stable or a specific version.

Lingua principale
Go
Stelle
354
Fork
221
Merge medio
4g 13h
PR unite (30g)
11

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dapr/cli

Tutte le issue di dapr/cli

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.