Repository navigation
chore(release): 2.2.1 - #28
Merged
Merged
Conversation
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
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.
What and why
Spawner 2.2.1: updates from 2.1 that keep every URL answering (#27), and
spawner upsending the git repositories cloned inside a project (#26). The changelog's section is the release notes;scripts/release.sh 2.2.1set the versions and taggedchore(release): 2.2.1.Merge with a merge commit: the tag
v2.2.1is on that commit, and the Release workflow refuses a tag that is not on master. Thengit push origin v2.2.1.Checks
CHANGELOG.mdupdated when the behaviour changesThe digests of
POSTGRES_IMAGEandTRAEFIK_IMAGEininstall.share thosepostgres:17-alpineandtraefik:v3.7have today: nothing to bump.