PE hyperstack: publish ghcr image on every main push#112
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.
Makes
ghcr.io/orkait/hyperstackalways serve the latest. Installs pull:main, but:mainwas going stale.Root cause
publish.ymlgated the Docker build + push onversion-is-new. So the image only rebuilt on the exact push where the version tag flipped - any other main merge left:mainpointing at an old build. The 1.1.0 image was never pushed (the #111 run was verify-only, 52s).Fix
:main+:shaonly:main,:latest,:<version>,:shaNow every merge to
mainrefreshes:mainand:latest;:<version>lets users pin a release. Actions are already enabled, so this self-heals - merging this PR triggers the workflow and produces the 1.1.0 image.Follow-up (one-time, needs packages admin)
After the first push, set the GHCR package
orkait/hyperstackvisibility to Public so anonymousdocker pull :mainworks for installers (Settings -> Packages, or API withwrite:packages).Verification
python3 -c "import yaml; yaml.safe_load(...)"passes; only the release-create step remains version-gated.