*: tag-minor-release-candidate gh action #4100
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4100 +/- ##
==========================================
+ Coverage 56.37% 56.38% +0.01%
==========================================
Files 245 245
Lines 31169 31169
==========================================
+ Hits 17571 17575 +4
+ Misses 11284 11283 -1
+ Partials 2314 2311 -3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new GitHub Actions workflow for automating the creation of minor release candidate tags. The workflow finds the latest release branch (e.g., main-vX.Y), determines the appropriate version prefix (vX.Y.0), identifies the most recent release candidate tag, and creates/pushes the next incremental RC tag.
Key Changes
- Automated release candidate tagging workflow with version detection
- Sequential RC numbering from existing tags (e.g.,
vX.Y.0-rc1→vX.Y.0-rc2) - Comprehensive workflow summary with next steps guidance
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
DiogoSantoss
added
the
merge when ready
Introduces
tag-minor-release-candidate.ymlGH action.This action finds the latest release branch (ideally, created from
bump-minor-version.yml#4084) such asmain-vX.Y, creates a version prefixvX.Y.0, finds the latest release candidate for this version such asvX.Y.0-rcZand creates/pushes a new release candidate tagvX.Y.0-rc(Z+1).category: misc
ticket: #3933