Publish Release images to GHCR in existing release workflow - #373
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
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.
Release images currently ship only as archive assets, so container platforms cannot pull them directly. Extend the existing
core-releaseGitHub Actions release job to load those same artifacts and publish Core, Web, Runtime and ingress to GHCR before publishing the GitHub Release. No rebuild or installer change is involved.Use fixed version tags, verify archive and registry image identities across Docker stores, and reuse existing tags only when they match. Manual drafts do not publish images. Failed pushes leave the Release as a draft; the existing recovery procedure reuses the original artifacts. Record digest-pinned image references in the job summary and isolate registry credentials to the release job.
Document the one-time administrator step to make each newly created GHCR package public. PostgreSQL stays upstream; no platform deployment templates or floating tags are introduced.
Validation:
make check-docs,make check-names,git diff --checkpassed.Live GHCR publication has not been exercised locally. The version-tag release workflow performs the real push after merge; anonymous pulls require the documented package visibility change.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.