CI(release): create reusable workflow for releases #9806
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.
Problem
We have a bunch of duplicated code for automated releases. There will be even more once we have
release-compute
branch (#9637).Another issue with the current
release
workflow is that it creates a PR from the main as is. In case we create 2 different releases from the same commit, GitHub could mix up results from different PRs.An internal example: https://neondb.slack.com/archives/C036U0GRMRB/p1732026358686539
Summary of changes
Tested: https://github.com/neondatabase/neon/actions/runs/11920553827/job/33222747567 / #9807