Chore: Update GA for rollups docker image publishing #14
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.
Summary
Changes to streamline rollups docker image generation. I also include a
release
with information about the current strategy, including the new one for rollups docker image publishing. More details are below.What is published to
ghcr.io
:rollups
or anypackages
will trigger the GA that publishes an image of your code tagged as pr-<number>main
branch changesrollups
and/or anypackages
it will publish an image tagged asedge
. That is a common tag that means access to fresh features, but it may be unstable.rollups@a.b.c
the image will be generated tagged as the versiona.b.c
and also taglatest
What is published to
docker.io
rollups@a.b.c
the image will be generated tagged as the versiona.b.c
and also taglatest
Architectures: Currently generating for
linux/amd64
andlinux/arm64