← Back to issue list

Embedded version required in snapcraft.yaml

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1594794
Type
issue
State
open
Author
~stub
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request from 2014 to let snapcraft.yaml's version key reference a part name so the version is derived from the plugin (e.g. Python setup.py) for Launchpad auto-builds. 10 years old, zero comments, no labels, no maintainer engagement; targets obsolete snapcraft 1.x.

Suggested action: close stale

Reason: The issue is 3723 days old (~10 years) with last activity 3500 days ago, 0 comments, no labels, and an external contributor, showing zero maintainer engagement. Its example (plugin: python3, source: lp:juju-deployer) reflects the snapcraft 1.x era, which has since been rewritten multiple times (craft-parts-based 7.x), and the proposed mechanism (version key accepting a part name) was never adopted, so the request as written no longer maps to the current architecture.

Impact: 25 Quick Win: 15.0 Staleness: 95 Complexity: 40 Confidence: 55 Support Request: 20

Issue body

snapcraft.yaml requires the version key, which is often redundant. Plugins will often know the version number (such as encoded in Python setup.py files), but that is just for a single part. Perhaps the version should optionally accept a part name instead of a version number, causing the version number of the part as reported by the plugin to be used for the snap (or an error raised if the plugin does not support it). The main use case would be have snap version numbers matching upstream for automatic builds, such as done by Launchpad. name: juju-deployer summary: Juju deployment lifecycle management description: Juju deployment lifecycle management version: juju-deployer apps:     juju-deployer:         command: juju-deployer parts:     juju-deployer:         plugin: python3         source: lp:juju-deployer

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 25
Quick Win: 15.0
Staleness: 95
Complexity: 40
Confidence: 55
Support Request: 20
close stale Feature request from 2014 to let snapcraft.yaml's version key reference a part name so the version is derived from the plugin (e.g. Python setup.py) for Launchpad auto-builds. 10 years old, zero comments, no labels, no maintainer engagement; targets obsolete snapcraft 1.x.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 20
Confidence: 90
Support Request: 10
close stale Request to let snapcraft.yaml version field pull version from a part instead of a hardcoded string. Currently inactive for over 10 years with no maintainer feedback.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 35
Confidence: 92
Support Request: 10
close stale Feature request to allow snapcraft.yaml version to dynamically reference a part's version instead of requiring a hardcoded value. Issue is over 10 years old with no maintainer response or activity.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 50
Confidence: 85
Support Request: 10
close stale Feature request to allow snapcraft.yaml version to reference a part's plugin-extracted version instead of a hardcoded string. Unaddressed for over 9 years with no maintainer interaction.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 30
Confidence: 92
Support Request: 10
close stale Proposes allowing snapcraft.yaml to auto-extract version numbers from parts instead of requiring manual embedding. Enables automatic upstream version matching. Open with zero comments and no activity for over five years.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1662634 Please add snapcraft version key snapcraft (launchpad) open Feature request to add a snapcraft-version key to snapcraft.yaml so users on older snapcraft get a clear 'Snapcraft X required' message instead of a cryptic schema error. Open ~9.5 years with zero comments, no labels, and no maintainer engagement.
77%