Repository navigation
Catalog build: take package-ci from the resolved core version - #29
Merged
Merged
Conversation
…t builds against, not from the release published last.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fetch-package-ci.sh took the bundle from the release published last (7.0.13, a 7.0 builder without the modes field), not from the core version catalog.yml resolves (7.1.0.beta2). The 2026-11-02 catalog run therefore dropped modes from every package. The script now honours --ref for the bundle, and catalog.yml passes the resolved version (not when it is the 0.0.0 fallback). Same change in shopclass-themes.