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.
Pushes the version tags to docker hub on a tag release
This will allow container users to choose the newest 22 without having to adapt to each minor or patch version manually. If the latest 22 is buggy, they can jump back to either a patch or a minor version until there is a new 22 version that fixes it.
When the tag version is the highest major version and is not the first major release with minor and patch version is 0 than it also creates a latest and stable tag.
Just to give an overview, here are some examples:
Release 22.5.1 on greenbone/boreas would result in the following tags:
Release 23.0.0 on greenbone/boreas would result in the following tags:
Release 23.0.1 on greenbone/boreas would result in the following tags:
Release 22.5.2 when there is already a 23.0.1 version available would result in the following tags: