← Back to issue list

Checking the compatibility tag should be more robust

View original Github issue

Metadata

Project
craft-providers
Number
#789
Type
issue
State
open
Author
bepri
Labels
Type: Enhancement
Created
Updated
Closed
—

Current evaluation

Enhancement to raise an error when compatibility tag is missing instead of assuming compatibility. Open for ~1 year with no maintainer comments or action.

Suggested action: needs triage

Reason: The issue has been open for ~1 year with 0 maintainer comments, no assignee, and no labels beyond the initial Type: Enhancement. The code at craft_providers/base.py:193-204 still contains the behavior described (assuming compatibility when config.compatibility_tag is None). Without maintainer engagement or discussion about whether this should be an error or warning, it needs triage to determine priority and scope.

Impact: 40 Quick Win: 28.0 Staleness: 75 Complexity: 30 Confidence: 65 Support Request: 10

Issue body

### What needs to get done Currently, when there is no compatibility tag (missing file, set to "None", or empty config), an assumption is made that the base in question is compatible. It should instead be investigated and potentially raised as some sort of error. ### Why it needs to get done It is bad to proceed without knowing whether or not the base is compatible!

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6
Impact: 40
Quick Win: 28.0
Staleness: 75
Complexity: 30
Confidence: 65
Support Request: 10
needs triage Enhancement to raise an error when compatibility tag is missing instead of assuming compatibility. Open for ~1 year with no maintainer comments or action.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 30
Confidence: 80
Support Request: 5
needs triage Enhancement to make compatibility tag validation more robust by raising an error instead of assuming compatibility when the tag is missing, empty, or None. Currently unaddressed and inactive.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 30
Confidence: 80
Support Request: 5
needs triage Enhancement to make compatibility tag validation more robust. Currently, missing or empty tags default to assuming compatibility instead of raising an error. Open with no maintainer comments.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 30
Confidence: 85
Support Request: 10
needs triage Enhancement to make compatibility tag validation more robust. Currently assumes compatibility when the tag is missing or empty, but should raise an error instead. Unassessed and inactive for over 10 months.

Update history

No update history recorded yet.

Related work

  • Related To: craft-providers#383 (confidence 60%)

    Related issue about compatibility tag handling, but focuses on test hardcoding rather than missing tag error handling.

Related issues

Issue Project State Summary Similarity
#383 bumping the compatibility tag should be more robust craft-providers open Enhancement to avoid hardcoding compatibility tags in tests by referencing them from a single source. Open for 3 years with no maintainer comments.
86%