Add how-to guide for upgrading Dagger
Documents the correct two-phase upgrade procedure to avoid the chicken-and-egg problem where CI can't build its own replacement. Also fixes outdated version references in the Dagger reference card. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
e95fb9a555
commit
ba7236ade0
4 changed files with 119 additions and 2 deletions
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Dagger
|
||||
modified: 2026-02-22
|
||||
modified: 2026-03-06
|
||||
tags:
|
||||
- reference
|
||||
- ci-cd
|
||||
|
|
@ -80,7 +80,7 @@ In [[forgejo]] Actions, secrets are injected as env vars. Locally, mise tasks ca
|
|||
|
||||
## Caveats
|
||||
|
||||
- **Pre-1.0 API** — Current version is v0.19.x. Pin the CLI version and test upgrades on a branch before adopting.
|
||||
- **Pre-1.0 API** — Current version is v0.20.x. Pin the CLI version and test upgrades on a branch before adopting. See [[upgrade-dagger]] for the upgrade procedure.
|
||||
- **Privileged container** — The Dagger engine requires privileged container access. The Forgejo runner's DinD sidecar provides this.
|
||||
|
||||
## Related
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue