Repository navigation
feat(ci): support separate native release aliases - #43
Merged
Merged
Conversation
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.
Pull Request
Description
Allow repositories that ship a Native API and a separate JVM worker to publish verified Native semantic aliases with an optional
alias-prefix. Maps usesnative-1.11.0alongside the existing JVM worker1.11.0tag, avoiding concurrent overwrites while reusing the existing tested-image publication flow. The default preserves all current callers and qualified immutable Native SHA tags.Type of Change
Related Issues
Completes Native migration of the additional Core services and execution roles requested after the first nine Game backends.
Testing
20 workflow contract tests pass. New tests first failed on the existing publisher, then passed with this change: main/release/prerelease aliases, unchanged immutable image tags, invalid prefix rejection before registry access, and Docker's 128-character tag limit. Existing secret-stdin, tested-image identity, PR publication guard, credential-file cleanup and no-rebuild contracts continue to pass.
Risk
Optional input changes only aliases in the existing publication step. Prefix validation occurs before registry login or push; unchanged callers retain previous behavior. No deployment or credential changes.
How to revert
Keep existing callers pinned to their prior immutable workflow commit; Maps can retain its previous JVM deployment until a compatible Native release is verified.
Checklist