feature request: charmcraft release=last-revision
Metadata
Current evaluation
No code change was needed: charmcraft upload <charm> --release=edge already uploads and releases the newly created revision.
Resolution: closed not a bug
Reason: Maintainer facundobatista explained on 2021-06-04 that the existing upload option provides the requested behavior. The request was answered with usage guidance rather than implemented or fixed.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Maybe I am missing something, but this is my current workflow:
```bash
$ charmcraft upload slurmd.charm
Revision 12 of 'slurmd' created
$ charmcraft release slurmd --revision=12 --channel=edge
Revision 12 of charm 'slurmd' released to edge
```
For the `release` step, I need to manually type the revision number. I'd like to have something like `charmcraft release revision=last --channel=edge` to release the latest uploaded charm.
`revision=last` may not be the best CLI parameter, an alternative could be `revision=-1`.
But even better would be `charmcraft upload slurmd.charm --release --channel=edge`.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | No code change was needed: charmcraft upload <charm> --release=edge already uploads and releases the newly created revision. | |
| stealth/space-bunny-alpha | — | closed not a bug | Feature request for `release --revision=last` closed: maintainer facundobatista pointed out the existing `charmcraft upload <charm> --release=edge` already uploads and releases the new revision, so no change needed. | |
| stealth/space-bunny-alpha | — | closed not a bug | Already supported: upload with --release=edge to release the newly uploaded revision, avoiding manual revision numbers; no code change was needed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as already implemented. The requested auto-release feature already exists via the --release flag on the upload command, as noted by a maintainer. No code changes were needed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as redundant. A maintainer noted the requested functionality already exists via the --release flag on the upload command, allowing automatic release of the latest revision without manual specification. | |
| qwen/qwen3.6-35b-a3b | — | — | Feature request to auto-release the latest charm revision was closed. Maintainer resolved it by noting the functionality already exists using the --release flag during upload, making the new parameter unnecessary. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as already implemented. The requested automatic release workflow is supported via the --release flag on the upload command, e.g., charmcraft upload <charm> --release=edge. No code changes required. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #126 Add a "--release" option to the "upload" command | charmcraft | closed | Implemented charmcraft upload --release in canonical/charmcraft#255 (merge 9064a3f3, feature bc06a62a); #457 added resource support and shipped in Charmcraft 1.1.2. | |
| #1979 `charmcraft upload` should allow a user to also release the charm | charmcraft | open | Requests single-command charm upload+release with automatic OCI resource handling. --release flag already exists; remaining gap is resource upload by image reference instead of revision number. | |
| #456 charmcraft upload foo.charm --release=edge gives internal error | charmcraft | closed | Fixed the upload --release regression in PR #457, merged as b5d735b4 and shipped in Charmcraft 1.1.2 to the candidate and edge channels. | |
| #679 Charmcraft should allow resource revisions == 0 when specifying uploads | charmcraft | closed | Resource revision 0 was accepted during `charmcraft release` uploads via merged PR canonical/charmcraft#682. |