Emit a warning when the fetch-service integration is enabled
Metadata
Current evaluation
Request to emit a warning when the fetch-service integration is enabled, so users know it is experimental. The warning was implemented in PR #496 and is present in the code; the issue is resolved but not yet closed.
Suggested action: close stale
Reason: The requested warning is already implemented: craft_application/services/fetch.py emits 'Warning: the fetch-service integration is experimental...' and merged PR #496 'feat: mark the fetch-service integration as experimental' resolved this (with a matching test_warning_experimental). Since the feature was implemented, the issue is no longer actionable.
Impact:
30
Quick Win:
25.5
Staleness:
55
Complexity:
15
Confidence:
85
Support Request:
5
Issue body
### What needs to get done
Communicate to the user that the integration is experimental and prone to change
### Why it needs to get done
Now that this work is merged into craft-application we want the users to be aware of the "alphaness" of the feature
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
25.5
Staleness:
55
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Request to emit a warning when the fetch-service integration is enabled, so users know it is experimental. The warning was implemented in PR #496 and is present in the code; the issue is resolved but not yet closed. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
10
Confidence:
75
Support Request:
0
|
needs triage | Unlabelled maintainer-requested task to add a warning for the experimental fetch-service integration. Inactive for over 1.8 years with no maintainer assessment or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
78
Complexity:
15
Confidence:
80
Support Request:
0
|
needs triage | Task to add a warning for an experimental fetch-service integration. Unlabelled and inactive for over a year, awaiting maintainer triage and prioritization. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
10
Confidence:
80
Support Request:
0
|
close stale | Add a warning when the fetch-service integration is enabled to inform users it is experimental. The issue remains open, inactive for 389 days, and is linked to internal Jira ticket CRAFT-3384 awaiting implementation. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-application#496
(confidence 90%)
PR #496 added the experimental warning and its unit test, resolving this issue
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #496 feat: mark the fetch-service integration as experimental | craft-application | merged | Merged pull request marking the fetch-service integration as experimental by hiding its CLI option and adding a development warning. Approved by three reviewers, passed CI, and resolved issue #488 with 30 additions and 7 deletions across three files. |