feat: validate devel bases with craft-application
Metadata
Current evaluation
Superseded by pull request #4796. The changes to validate devel bases with craft-application and remove the build-base: devel requirement for core24 snaps were closed in favor of the newer implementation.
Suggested action: —
No scores available.
Issue body
- [ ] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox run -m lint`?
- [ ] Have you successfully run `tox run -e test-py310`? (supported versions: `py39`, `py310`, `py311`, `py312`)
-----
For https://github.com/canonical/craft-application/pull/302 and https://github.com/canonical/craft-application/issues/298
This has the side-effect that `build-base: devel` is no longer required for `core24` snaps.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Superseded by pull request #4796. The changes to validate devel bases with craft-application and remove the build-base: devel requirement for core24 snaps were closed in favor of the newer implementation. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and superseded by PR #4796. Originally drafted to wait for a craft-application release before validating devel bases, changes were consolidated into the newer PR instead. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by PR #4796. The feature to validate devel bases with craft-application and remove the core24 build-base requirement was held pending a craft-application release, then closed in favor of the replacement pull request. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #532 feat: validate devel bases with craft-application | rockcraft | closed | Superseded and completed via PR #569. The PR was held as a draft pending a craft-application release before being resolved through the follow-up pull request. | |
| #302 feat!: validate devel bases | craft-application | merged | Merged implementation of devel base validation for craft applications. Approved by reviewers, passed CI checks, and updated to target Ubuntu 24.10. Resolves #298 with 324 additions and 98 deletions across nine files. | |
| #1634 feat: validate devel bases with craft-application | charmcraft | closed | Abandoned without merging. Upstream craft-application changes made the validation unnecessary. The author noted the work may be revisited once craft-application issue #348 is resolved. | |
| #761 models/project.py: do not check for base when build-base: devel | craft-application | closed | Rejected. Maintainers kept the default base validation for all crafts. They advised overriding _validate_devel_base in snapcraft to support the gadget snap use case instead. | |
| #4562 Validity of `base` is not checked when using `--destructive-mode` | snapcraft | closed | Resolved in snapcraft 8.1 via craft-application 2.0 and canonical/craft-application#263. Base validity is now enforced during destructive-mode builds, blocking invalid or unreleased bases. | |
| #298 Mechanism to handle/promote 'devel' bases | craft-application | closed | Closed without implementation. The proposal to centralize devel base validation in craft-application and update dependent projects was not addressed. Synced to Jira as CRAFT-2675, but no fix or follow-up pull request was created. | |
| #4873 feat: support "build-for: [all]" in core24 | snapcraft | merged | Merged implementation of build-for: [all] support for core24 snaps, fixing #4854. Changes were squashed, craft-application updated to 3.0.0, and unit and spread tests added after two approvals. |