feat: Generate :next
and :edge
docker tags
#1141
Merged
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.
📁 Related issues
#1140
✍️ Description
This PR will add 2 new docker tags to the official docker image by updating the CI.
branch:
main
docker tag:
:edge
This tag would be generated on each commit push on the
main
branch. The idea is that you can have a docker image of the latest developments. I suggest:edge
in favor of the earlier proposed:dev
tagname, because it better self-explains what it is. It is on the edge of the main repository. If you need that for development, you'll pick it.If we were to use the
:dev
tag, you first have to at least find out what that really means.branch:
versions/*
docker tag:
:next
This tag would be generated on each commit push on the
versions/*
branch. There should only be one version there that is being prepared. This tag will guarantee an image with the latest upcoming version features.✅ PR check list
Before this pull request can be merged, a core maintainer will check whether