← Back to issue list

Scheduled/manual Spread snap build fails when generated version exceeds 32 characters

View original Github issue

Metadata

Project
rockcraft
Number
#1336
Type
issue
State
open
Author
gcomneno
Labels
—
Created
Updated
Closed
—

Current evaluation

Snap-build fails when setuptools_scm post-release version exceeds 32 chars. Acknowledged by maintainer, confirmed with fresh reproduction.

Suggested action: keep open

Reason: Maintainer @lengau acknowledged the issue ('We were aware of the length limit...but not that we were running up against it') and the reporter confirmed with a fresh reproduction on 2026-09-06. The issue is clearly scoped with a valid bug (snap-build fails when version exceeds 32 chars) and has recent activity.

Impact: 55 Quick Win: 30.25 Staleness: 20 Complexity: 45 Confidence: 75 Support Request: 10

Issue body

The `Spread (manual - large/flaky)` workflow currently fails during `snap-build` on `main`. I first noticed this on a scheduled run from my fork, then synced the fork to current `canonical/rockcraft:main` (`d9756725`) and reproduced it with a fresh `workflow_dispatch` run: https://github.com/gcomneno/rockcraft/actions/runs/32214626147 The build generates: `1.17.0.post132+gd975672.d20260819` Snapcraft then rejects it because the generated version is 33 characters long: `Value should have at most 32 items after validation, not 33` This causes `snap-build` to fail and `snap-tests` to be skipped. Just flagging this in case it isn't already on the team's radar.

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6
Impact: 55
Quick Win: 30.25
Staleness: 20
Complexity: 45
Confidence: 75
Support Request: 10
keep open Snap-build fails when setuptools_scm post-release version exceeds 32 chars. Acknowledged by maintainer, confirmed with fresh reproduction.
qwen3.6-35b-a3b-mtp-q6
Impact: 65
Quick Win: 35.75
Staleness: 35
Complexity: 45
Confidence: 75
Support Request: 10
keep open CI snap-build fails because generated version string exceeds snapcraft's 32-character limit; maintainer acknowledged the issue.
qwen/qwen3.6-35b-a3b
Staleness: 5
Complexity: 30
Confidence: 85
Support Request: 10
needs triage CI workflow fails during snap-build because auto-generated version strings exceed snapcraft's 32-character limit. Acknowledged by maintainer, currently under discussion with no labels or assignee.
qwen/qwen3.6-35b-a3b
Staleness: 5
Complexity: 25
Confidence: 90
Support Request: 5
needs triage CI workflow fails during snap-build because the generated version string exceeds snapcraft's 32-character limit, causing builds to fail and tests to be skipped. Currently unlabelled and awaiting maintainer review.

Update history

Date Change
updated
updated
created

Related work

  • Related To: canonical/starbase#337 (confidence 85%)

    Issue body explicitly references this as a related concern: 'This will likely cause us issues with https://github.com/canonical/starbase/issues/337 as well.' starbase#337 is about the deprecated setuptools-scm post-release version scheme, which is the root cause of the long version strings.

Related issues

No related issues found above the similarity threshold.