Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Automate patch releases and pre-releases (v12) #3499

Merged
merged 1 commit into from
May 9, 2024

Conversation

wolfgangwalther
Copy link
Member

This is a back-port of #3485 and its follow-up commits. This will allow us to release a new patch-release for v12 before we make a new minor release.

This includes the following commits:

Making a new release on the back-branch should be as easy as pushing a commit which bumps the version in postgrest.cabal. We will see how that goes in #3443.

This work by automatically pushing a new tag on main and release
branches after each commit. The tag will be "devel" on main and the
version from postgrest.cabal for release branches. The release
workflow then runs as a tag pipeline, making the actual release.

For release branches, the tag will only be created if a tag for this
version doesn't exist, yet. This means to actually make a new patch
release, we still need to bump the version in postgrest.cabal. We
can automate this later as part of our backport-bot.

This is a back-port of the following commits:
- dd8d51a
- fe0f2f7
- 58d8133
- 9fe90bf
- c67f1c3
- 8433f98
- d9ba9a8
- a57d12b
- b006016
@wolfgangwalther wolfgangwalther merged commit ac217c1 into PostgREST:v12 May 9, 2024
34 checks passed
@wolfgangwalther wolfgangwalther deleted the backport-ci-v12 branch May 9, 2024 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant