Repository navigation
fix(ci)!: validate Melange runner profiles - #65
Merged
Merged
Conversation
Resolve standard and large profiles on a fixed runner before scheduling builds. Reject unsupported profiles and legacy runner-label configuration. Runner access policies remain unchanged. BREAKING CHANGE: new callers must replace runner with runner-profile and migrate their catalog together with the planner and workflow pins. Existing SHA-pinned callers are unaffected.
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
1 participant
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.
Melange builds currently accept arbitrary runner labels from caller configuration. This change resolves standard and large profiles to fixed architecture-specific runners in a separate validation job before scheduling the build. Runner-group policies and existing SHA-pinned workflows retain their current behavior.
BREAKING CHANGE: callers adopting this Factory revision must replace the Melange runner input with runner-profile, remove legacy Melange runner-label keys, and update the planner and reusable-workflow pins together. Smoke runner configuration is unchanged. Migration instructions are included in actions/apko-plan/README.md.
Validation: planner regression tests, all four supported runner mappings, malformed and injected input rejection, and Actionlint pass.