← Back to issue list

schema: remove support for os when using bases

View original Github issue

Metadata

Project
snapcraft
Number
#2626
Type
pull request
State
merged
Author
sergiusens
Labels
—
Created
Updated
Closed

Current evaluation

Successfully merged pull request removing os type support from the schema when using bases, as base support supersedes it. Approved by reviewer, passed CI checks, and integrated.

Suggested action: —

No scores available.

Issue body

Base support superseed the os type which should stay in legacy. Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com> - [ ] 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 `./runtests.sh static`? - [ ] Have you successfully run `./runtests.sh tests/unit`? -----

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — — Successfully merged pull request removing os type support from the schema when using bases, as base support supersedes it. Approved by reviewer, passed CI checks, and integrated.
qwen3.6-35b-a3b-mtp-q6 — — Merged PR removes the os schema type when bases are specified, as base support supersedes it. The os field remains for legacy configurations.
qwen3.6-35b-a3b-mtp-q6 — — Merged. Removes schema support for the os field when bases are used, as bases supersede it. The os field remains in legacy mode.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#2344 schema: remove the deprecated snap keyword for bases snapcraft merged Merged into master, the schema no longer uses the deprecated snap keyword for bases, replacing it with prime. Approved by two reviewers, passed CI, and increased coverage by 0.04%.
74%
#1004 fix: unhelpful error message when `base` is missing from YAML rockcraft merged Merged a fix that improves the error message when the base field is missing from YAML, resolving issue 997. Approved by two reviewers, the PR passed CI checks aside from unrelated known failures, and was successfully integrated.
70%