add a "version" option on charmcraft release cli
Metadata
Current evaluation
Rejected. The store determines version from the artifact itself, not CLI input. Dynamic version extraction from charm metadata is under separate consideration.
Suggested action: —
No scores available.
Issue body
Personally, I think it would be great for charm developers if we have an option of passing the charm version in the CLI.
This would faciltate the CI/CD and would stop the need of creating a `version` file before using `charmcraft pack`
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected. The store determines version from the artifact itself, not CLI input. Dynamic version extraction from charm metadata is under separate consideration. | |
| qwen/qwen3.6-35b-a3b | — | — | Rejected as not feasible; the store retrieves version directly from the charm artifact. The team is separately evaluating dynamic metadata inclusion instead. | |
| qwen/qwen3.6-35b-a3b | — | — | Rejected as not feasible. The store retrieves version directly from the charm artifact, making a CLI option unnecessary. Maintainers are separately considering dynamic version extraction from charm metadata. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected. The store retrieves versions directly from charm artifacts, making a CLI option unfeasible. Maintainers are exploring dynamic version extraction from charm metadata separately. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected. The store retrieves version data directly from the charm artifact, making a CLI flag unfeasible. The request was closed. Future work may explore dynamically extracting version metadata separately. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #37 Populate the 'version' file as part of 'charmcraft build' | charmcraft | closed | Rejected. The team decided against auto-generating a version file due to evolving Juju/Charmhub versioning semantics. Developers must create the file in their build pipeline; charmcraft preserves existing version files during packaging. | |
| #1790 Set a charm version from `charmcraft.yaml` | charmcraft | open | Feature request to accept a version field in charmcraft.yaml and store it in the output charm. Open 755 days with no comments or labels; blocked on design decisions about where Juju should read the version from. |