← Back to issue list

Allow including resources when releasing charms directly in the upload command (CRAFT-381).

View original Github issue

Metadata

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

Current evaluation

Merged. Enables including resources when releasing charms via the upload command, fixing issue #456 and CRAFT-381. Approved by two reviewers with 63 additions across three files. Maintainers prioritized CI workflow improvements.

Suggested action:

No scores available.

Issue body

Fixes 456.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Merged. Enables including resources when releasing charms via the upload command, fixing issue #456 and CRAFT-381. Approved by two reviewers with 63 additions across three files. Maintainers prioritized CI workflow improvements.
qwen3.6-35b-a3b-mtp-q6 Merged to fix issue #456. Enables including resources directly in the charm upload command. Maintainers accepted the implementation for CI/CD support, deferring stricter error handling and documentation updates.
qwen3.6-35b-a3b-mtp-q6 Merged to resolve issue #456. Enables including resources when releasing charms directly via the upload command. Maintainers approved the implementation as-is for stable, deferring stricter validation and documentation updates to future discussions.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#259 Support for attaching resources when releasing charms. charmcraft merged Merged after two approvals. Adds support for attaching resources during charm releases, modifying seven files with 188 additions and 26 deletions to update the release workflow.
82%
#255 Add the option to release when uploading a charm or bundle charmcraft merged Merged to add an option for releasing charms or bundles during upload. Approved by one reviewer, the change modifies three files with 80 additions and 8 deletions.
78%
#1313 Make it easier to release charms in CI and in general charmcraft open Feature request to upload and release a charm plus its OCI resources in one command without tracking integer revision IDs. Skopeo integration landed, but upload --resource still requires name:revision format. Maintainers acknowledge it remains applicable and UX is being considered across crafts.
73%
#682 Allow for resources with a rev of 0 during `charmcraft release` charmcraft merged Merged to allow resources with revision 0 during charmcraft release. Resolves issue #679. Approved by one reviewer with minimal changes across two files.
73%
#847 Improve the 'release' response when resources are automatically released with the charm charmcraft open Request to enhance the 'charmcraft release' command output to list resources that Charmhub automatically attaches when a revision is released without explicit --resource flags. Store-side fix was released in 2022, but the client-side message enhancement remains unimplemented.
71%
#2172 docs: update release step with resource details charmcraft merged Merged documentation update adding resource attachment details to the charm release example, resolving issue #2171. Standardizes charm names across the Publish section. Approved by two reviewers, passed CI, and applied with a minimal eight-line change.
71%
#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.
70%