feature request: charmcraft release=last-revision
Metadata
Current evaluation
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.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as already implemented. The requested auto-release functionality is available via charmcraft upload <charm> --release=<channel>, as noted by a maintainer. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1979 `charmcraft upload` should allow a user to also release the charm | charmcraft | open | Feature request to add --release flag to charmcraft upload command. The --release flag is already implemented (PR #255), but auto-uploading resources from upstream-image field in charmcraft.yaml remains unimplemented. Last activity Feb 2025. |