component does not take snap version when no version provided
Metadata
Current evaluation
Component version inheritance was triaged as an enhancement; maintainers adopted component-level adopt-info, and follow-up #5240 was closed after implementation merged in canonical/snapcraft#5753.
Suggested action: close resolved
Reason: The maintainer explicitly selected component-level adopt-info as the strategy and linked it to follow-up #5240. The tracker records #5240 as closed and states that component version adoption was implemented and merged via canonical/snapcraft#5753, addressing the request through explicit adoption rather than implicit inheritance.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
19
Complexity:
55
Confidence:
97
Actionability:
92
|
close resolved | Component version inheritance was triaged as an enhancement; maintainers adopted component-level adopt-info, and follow-up #5240 was closed after implementation merged in canonical/snapcraft#5753. | |
| stealth/space-bunny-alpha |
Impact:
52
Quick Win:
21
Complexity:
57
Confidence:
93
Actionability:
94
|
close resolved | Component version adoption was implemented through per-component adopt-info, superseding the original request for automatic snap-version inheritance. | |
| qwen/qwen3.6-35b-a3b |
Impact:
70
Quick Win:
22
Complexity:
60
Confidence:
90
Actionability:
80
|
close resolved | Components should inherit snap version when no version is provided. Resolved by implementing adopt-info for components via PR #5753. | |
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
22
Staleness:
25
Complexity:
55
Confidence:
72
Support Request:
5
|
keep open | Component version not inherited from snap when no explicit version is set. Triaged as enhancement; fix planned via component-level adopt-info support, scheduled for 25.10 cycle. Component adopt-info now appears in docs and code. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
45
Complexity:
60
Confidence:
90
Support Request:
10
|
keep open | Component version inheritance from snap version when not explicitly set. Issue is triaged with a planned implementation strategy relying on `adopt-info` support for components in a future release cycle. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
50
Complexity:
60
Confidence:
90
Support Request:
5
|
keep open | Enhancement to make components inherit the snap version when unspecified. Triaged and acknowledged; maintainers plan to implement via adopt-info support in a future release cycle. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
snapcraft#5240
(confidence 99%)
The maintainer moved the requested versioning behavior to the component adopt-info analogue tracked in #5240.
-
Likely Fixed By:
canonical/snapcraft#5753
(confidence 97%)
The #5240 tracker summary identifies this merged PR as the implementation of component version adoption.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5240 Add `adopt-info` analogue for components | snapcraft | closed | Implemented component version adoption via merged PR #5753 (commits 6b6f7d9ee, 766562286), allowing craftctl to set component versions in Snapcraft 8.13. | |
| #2080695 `adopt-info:` for components | snapcraft (launchpad) | closed | Feature request for adopting component versions via adopt-info was implemented in canonical/snapcraft PR #5753 (commits 6b6f7d9ee, 766562286), letting craftctl set component metadata. ClOSED as completed by ~mr-cal. |