fix: use artifact in fetch-service context
Metadata
Current evaluation
Merged a fix updating the fetch-service context for the artefact to artifact rename in v0.6. Approved by two reviewers, passed CI, and maintained full test coverage across six files.
Suggested action: —
No scores available.
Issue body
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox`?
Changes required to make fetch-service work after `artefact` -> `artifact` change (released in `v0.6`).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a fix updating the fetch-service context for the artefact to artifact rename in v0.6. Approved by two reviewers, passed CI, and maintained full test coverage across six files. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged #587 to align fetch-service with the v0.6 artifact rename. Resolves compatibility issues and passes all coverage checks. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #275 fix(service): apply same rules if artefact already downloaded | fetch-service | merged | Merged a fix ensuring consistent results for already downloaded artifacts across permissive and strict modes. Approved by three reviewers and passed CI checks before integration. | |
| #804 fix(test): fix fetch service integration test for changed string | craft-application | merged | Merged a fix for the fetch service integration test to accommodate a changed string. Approved by two reviewers, passed CI, and modified one file with three additions and two deletions. Linting fixes were handled separately. |