bumping the compatibility tag should be more robust
Metadata
Current evaluation
Enhancement to avoid hardcoding compatibility tags in tests by referencing them from a single source. Open for 3 years with no maintainer comments.
Suggested action: close stale
Reason: This 3-year-old enhancement request about test refactoring has received no maintainer engagement (0 comments) and the project has evolved through multiple compatibility tag versions (v3 to v8) since it was opened. The specific PR discussion referenced in the issue body is likely no longer applicable to the current codebase.
Impact:
30
Quick Win:
22.5
Staleness:
75
Complexity:
25
Confidence:
65
Support Request:
10
Issue body
### What needs to get done
Directly reference the compatibility tag from the tests, rather than hardcoding it.
See https://github.com/canonical/craft-providers/pull/382#discussion_r1297563019
### Why it needs to get done
When the compatibility tag needs to be bumped, it can be changed in 50 places in the test suite, but not all of them have to be changed. This is confusing and can be error prone.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
30
Quick Win:
22.5
Staleness:
75
Complexity:
25
Confidence:
65
Support Request:
10
|
close stale | Enhancement to avoid hardcoding compatibility tags in tests by referencing them from a single source. Open for 3 years with no maintainer comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
80
Complexity:
25
Confidence:
85
Support Request:
0
|
needs triage | Enhancement to refactor the test suite to dynamically reference a compatibility tag instead of hardcoding it in ~50 locations, reducing error-prone manual updates. Currently open with no maintainer comments or assignment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
70
Complexity:
20
Confidence:
75
Support Request:
0
|
needs triage | Enhancement to replace hardcoded compatibility tags in the test suite with dynamic references to prevent error-prone updates. Open for nearly three years with zero comments, awaiting maintainer triage. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
70
Support Request:
0
|
needs triage | Enhancement to replace hardcoded compatibility tags across ~50 test files with a single dynamic reference to simplify updates. Open for nearly three years with no maintainer comments or progress. |
Update history
No update history recorded yet.
Related work
-
Related To:
craft-providers#789
(confidence 70%)
Related issue about compatibility tag robustness but addresses runtime validation (raising errors when tag is missing) rather than test refactoring.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #789 Checking the compatibility tag should be more robust | craft-providers | open | Enhancement to raise an error when compatibility tag is missing instead of assuming compatibility. Open for ~1 year with no maintainer comments or action. | |
| #1010 fix: improve robustness of compatibility tag | craft-providers | open | PR improves compatibility tag handling by not assuming compatibility when tag is missing, refactors instance config loading into shared method with consistent error handling. Fresh PR (7 days old), passing CI, awaiting review. |