chore(bases): bump compatibility tag to v6
Metadata
Current evaluation
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.
Resolution: closed resolved
Reason: The change was merged into main by commit 69207f7, ensuring upgrades from 1.19.3 to 1.21.0 receive a new compatibility tag.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the guidelines for contributing?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `tox`?
-----
In preparation for releasing 1.21.0.
The compatibility tag has to be updated because of a confusing order of events. The compat tag was bumped to `v4` on `main` then later bumped to `v5` in a hotfix branch and merged into main:
```
1.19.3 (2023-12-01)
-------------------
- Update base compatibility tag to ``base-v5``.
...
1.20.1 (2023-11-30)
-------------------
- Update base compatibility tag to ``base-v4``
```
This bump to `v6` is to prevent a scenario where a user upgrades from `1.19.3` to `1.21.0` and gets the changes from `1.20.0` but doesn't get a new compat tag.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | 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. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Merged PR to bump the base compatibility tag to v6 for the 1.21.0 release, ensuring correct upgrade paths from 1.19.3. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/craft-providers#475
(confidence 95%)
The preceding v5 tag bump, merged as commit 1737c48, established the compatibility-tag sequence advanced by this PR.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #475 chore(bases): bump compatibility tag to v5 | craft-providers | merged | 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. | |
| #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`. | |
| #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. | |
| #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. | |
| #1516 chore(deps): update dependency hypothesis to v6.98.3 | charmcraft | merged | Renovate PR merged (commit 47776245), bumping the test dependency hypothesis from 6.97.1 to 6.98.3 in requirements.txt (+1/-1 line); approved by 2 reviewers, later superseded by further hypothesis bumps. | |
| #1007 chore(deps): update dependency pathspec to v0.11.0 | charmcraft | merged | Renovate PR bumping pathspec 0.10.3 -> 0.11.0 was approved and merged via commit 9b286165 (changes 9e1e9b08), a one-line pin update. |