← Back to issue list

Final commands changes for Bundles support.

View original Github issue

Metadata

Project
charmcraft
Number
#248
Type
pull request
State
merged
Author
facundobatista
Labels
—
Created
Updated
Closed

Current evaluation

Merged final Bundles CLI updates in charmcraft#248 via commit ab9f64c4 (merge commit 5e345875).

Resolution: closed resolved

Reason: PR #248 was merged as commit 5e345875, with implementation commit ab9f64c4. It made names mandatory for revisions and status and enforced a release name, exactly one revision, and one or more channels.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Explained changes (UX changes accoording to [this doc](https://docs.google.com/document/d/1dqzoFLEaB_1N_jJJdmsoCxeLUtTZRakveXF8aHx6lFA/)): - `revisions` and `status`: now `name` is mandatory (no longer guessed from metadata) - `release` now gets `name` as first mandatory parameter, then `--revision` as a mandatory option (only one allowed!) and `--channel` as mandatory option (multiple allowed).

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged final Bundles CLI updates in charmcraft#248 via commit ab9f64c4 (merge commit 5e345875).
stealth/space-bunny-alpha — closed resolved Merged Bundles CLI updates: revisions and status now require names; release requires name, exactly one --revision, and one or more --channel options.
qwen/qwen3.6-35b-a3b — — Merged CLI updates for Bundles support. Revisions and status now require a mandatory name. Release requires name first, plus mandatory --revision and --channel options. Approved by two reviewers and passed CI.
qwen3.6-35b-a3b-mtp-q6 — — Merged. Updates CLI commands for Bundles support: revisions and status now require a mandatory name parameter. The release command requires name as the first argument, with mandatory --revision and --channel options.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#235 Draft for the rest of bundle-related commands. charmcraft closed Closed unmerged as redundant: its author said all related bundle-command work was already landed. Final CLI updates were merged separately in charmcraft#248 (5e345875).
80%
#1858 Remove bundle commands charmcraft closed Bundle-specific commands/features were removed in merged PR #2320 (commit 2cb4db71, "feat!(bundle): remove bundle features") for Charmcraft 4.0; `type: bundle` now errors pointing to Charmcraft 3, closing #1858.
76%
#2320 feat!(bundle): remove bundle features charmcraft merged Merged as commit 2cb4db71: bundle pack/commands removed from Charmcraft 4.0; `type: bundle` now errors pointing users to Charmcraft 3. Closes #1858 (CRAFT-3990/CHARMCRAFT-623).
75%
#246 Support for bundles in the Upload command. charmcraft merged Merged PR #246 added bundle support to Charmcraft's Upload command, fixing #77 and advancing broader bundle-store support in #128 (commit 881bc0a8).
74%
#395 Update the default bundle from `charmcraft init` charmcraft merged Merged PR #395 as commit 18e8e71b, improving charmcraft init metadata and moving contributor guidance from README into CONTRIBUTING.md.
72%
#2305 feat!(bundle): remove bundle-specific store commands charmcraft closed Closed unmerged as superseded by #2320, merged as 2cb4db71; it removed bundle features and store commands in Charmcraft 4, directing bundle users to Charmcraft 3.
72%
#2113 Mark bundle commands as deprecated charmcraft closed Bundle commands were marked deprecated in canonical/charmcraft#2227 (commit 8b2a2bb2); promote-bundle was deprecated separately by #2226 (commit 00815ec4).
71%