edit-validation-sets makes it impossible to publish a new revision of an existing sequence (no override)
Metadata
Current evaluation
Regression where edit-validation-sets hard-blocked same-sequence revisions was fixed by merged PR #6420 (commit 2989b5f8b), restoring the non-blocking sequence warning from PR #5545 lost in the #6050 refactor.
Resolution: closed resolved
Reason: Maintainer mr-cal confirmed the non-blocking-warning behaviour had regressed when PR #6050 migrated validation sets to a service. PR #6420 ('fix: allow same-sequence validation set revisions', merged as commit 2989b5f8b) restored the PR #5545 behaviour and closed the issue; tracked internally as SNAPCRAFT-1378.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Regression where edit-validation-sets hard-blocked same-sequence revisions was fixed by merged PR #6420 (commit 2989b5f8b), restoring the non-blocking sequence warning from PR #5545 lost in the #6050 refactor. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #6420, restoring non-blocking sequence warnings so existing validation sets can be revised without incrementing their sequence. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed a regression where edit-validation-sets blocked publishing revisions without incrementing the sequence. The fix restores the non-blocking warning behavior from PR #5545, reversing a refactor in PR #6050. | |
| qwen/qwen3.6-35b-a3b |
Impact:
50
Quick Win:
40
Staleness:
10
Complexity:
20
Confidence:
85
Support Request:
0
|
keep open | Regression in edit-validation-sets blocking same-sequence updates; triaged, confirmed by maintainer, fix in progress. | |
| qwen/qwen3.6-35b-a3b |
Impact:
60
Quick Win:
42
Staleness:
10
Complexity:
30
Confidence:
85
Support Request:
0
|
keep open | Validation set editing blocks same-sequence revisions; maintainer confirmed bug and identified regression from PR #6050. Triaged, open. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
75
Quick Win:
52
Staleness:
5
Complexity:
30
Confidence:
90
Support Request:
0
|
keep open | Triaged bug where edit-validation-sets blocks updating a validation set revision without incrementing the sequence number. Maintainer confirmed regression from PR #6050. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
60
Quick Win:
36
Staleness:
0
Complexity:
40
Confidence:
70
Support Request:
30
|
needs triage | User reports snapcraft edit-validation-sets blocks publishing a new revision with the same sequence number; a confirmation prompt exists but defaults to N, and no --force flag is available. |
Update history
| Date | Change |
|---|---|
| closed | |
| updated | |
| updated | |
| updated | |
| updated | |
| updated | |
| updated | |
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#6420
(confidence 97%)
Merged PR restoring non-blocking sequence warnings, closing #6413
-
Caused By:
canonical/snapcraft#6050
(confidence 90%)
Service migration refactor that reintroduced the hard-failing sequence check
-
Superseded By:
canonical/snapcraft#5545
(confidence 85%)
Original PR #5545 (cb96b3533) implemented the ignore-warning behaviour that #6420 restored
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #6420 fix: allow same-sequence validation set revisions | snapcraft | closed | Merged as commit 2989b5f8b via PR #6420 (into hotfix/9.1), restoring the non-blocking sequence warning so edit-validation-sets can publish same-sequence revisions. Fixes #6413. | |
| #6412 edit-validation-sets refuses to create a new validation set at sequence 1 ("sequence number was not incremented") | snapcraft | open | edit-validation-sets rejects creating a brand-new validation set at sequence 1 because the sequence-increment check runs even when no existing set exists; confirmed by maintainer, tracked as SNAPCRAFT-1379. | |
| #6423 fix(validation-sets): don't validate new sets | snapcraft | closed | PR #6423 (SNAPCRAFT-1379) fixed edit-validation-sets rejecting brand-new validation sets at sequence 1; approved with no unresolved comments and landed as commit e7b47adb7, stacking on merged PR #6420. |