chore(bases): bump compatibility tag to v5
Metadata
Current evaluation
Merged PR #475 (commit 1737c48) bumping the craft-providers base compatibility tag from v4 to v5, rebased and merged into the hotfix/1.19 branch to expedite a hotfix release. Later superseded by v6 (#500), v7 (#513) and v8.
Resolution: closed resolved
Reason: The PR itself was merged via rebase-and-merge, landing as commit 1737c48 "chore(bases): bump compatibility tag to v5 (#475)", after the blocking fix in #473 was merged. Review was approved with no CI failures.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #475 (commit 1737c48) bumping the craft-providers base compatibility tag from v4 to v5, rebased and merged into the hotfix/1.19 branch to expedite a hotfix release. Later superseded by v6 (#500), v7 (#513) and v8. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Merged PR #475 bumping the compatibility tag to v5 in craft-providers to expedite a hotfix release. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Blocked By:
canonical/craft-providers#473
(confidence 92%)
PR body states "Blocked by #473", the LXD base instance cache-mount fix merged into hotfix/1.19.
-
Superseded By:
canonical/craft-providers#500
(confidence 78%)
Commit 69207f7 bumped the compatibility tag to v6, later followed by v7 (#513) and v8.
-
Related To:
canonical/craft-providers#465
(confidence 70%)
Commit 029c322 performed the equivalent v3 to v4 compatibility tag bump, showing the recurring pattern.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #500 chore(bases): bump compatibility tag to v6 | craft-providers | merged | Merged PR #500 as commit 69207f7, bumping the base compatibility tag to v6 for 1.21.0 to prevent incorrect upgrade paths from 1.19.3. | |
| #513 chore(bases): bump compatibility tag to v7 | craft-providers | merged | Merged as 37b0cf7: bumped Base.compatibility_tag from "base-v6" to "base-v7" across 7 base modules (41 lines), invalidating old instances because some image sources changed from `ubuntu` to `buildd`. | |
| #465 chore(bases): bump compatibility tag to v4 | craft-providers | merged | Merged PR #465 as commit 029c322, bumping the bases compatibility tag to v4 for the LXD PID/setup changes delivered in #464. | |
| #441 chore(bases): bump compatibility tag to v3 | craft-providers | merged | Merged #441 via commit f608f53, bumping base compatibility tags from v2 to v3 after a 1.16 timer incompatibility could prevent LXD instances from starting. | |
| #1004 chore(deps): update dependency craft-providers to v1.7.1 | charmcraft | merged | Renovate bumped craft-providers from 1.7.0 to 1.7.1 in charmcraft's pinned requirements. Merged via commit c598065f, landed through merge commit 6f35d244 (PR #1004). | |
| #1023 chore(deps): update dependency craft-providers to v1.7.2 | charmcraft | merged | Renovate PR #1023 was approved and merged, bumping the craft-providers pin from 1.7.1 to 1.7.2 in two requirements files (+2/-2 lines), as commit d1970b2d. | |
| #1294 chore(deps): craft-providers to v1.18.0 | charmcraft | merged | Dependabot-style bump of craft-providers to v1.18.0 merged to main via commit 59b70f01, changing the pin in two dependency files (+2/-2). Approved by 2 reviewers, no follow-up revert. | |
| #407 chore(deps): bump craft-providers | rockcraft | closed | Closed unmerged and superseded by canonical/rockcraft#420, which merged the craft-providers 1.20.0 update in commit 47e05667. | |
| #1560 chore: bump craft-providers to 1.23 | charmcraft | merged | Merged (commit 02980c7e) after two approvals; bumped craft-providers to 1.23.0 once published to PyPI, then Renovate PR #1610 (f8582941) bumped to 1.23.1. | |
| #1281 chore(deps): update dependency craft-providers to v1.18.0 - autoclosed | charmcraft | closed | Renovate's craft-providers 1.18.0 bump was auto-closed unmerged; the identical update landed via PR #1294 in commit 59b70f01, bumping the pin in two dependency files (+2/-2). |