Automatically release images #22
Merged
Conversation
This file contains 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
valentindeaconu
force-pushed
the
release-images-automatically
branch
from
202638d to
83ea292
Compare
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.
Automatically release images on pushes to master.
Changes made to this repository are, in most cases, created by the Renovate bot. Usually, they can be directly released, as they bump PocketBase/Litestream versions. They still need to be verified and release notes read before merging, so I will keep the PR workflow, but after merging the PR, the releases will be performed automatically by GitHub.
With this change, I'm aligning the image version with the underlying PocketBase version. So, a release of
pocketbase-litestream-dockerwith the namev0.23.0-ls0.3.13will represent a build with PocketBase version 0.23.0 and Litestream version 0.3.13.