-
Notifications
You must be signed in to change notification settings - Fork 0
Overwriting a development version with a release version #109
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
Conversation
…ttings along with the plugin version.
…o use contains function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR ensures that when releasing a new version the development build is correctly overwritten with the release version. It updates the release-drafter workflow to skip specific changelog update commits and conditionally run version update jobs.
- Added a conditional to skip the release draft update if the branch contains "doc/changelog-update-".
- Introduced a commit message check to determine whether to skip running the update_version job.
|
|
||
| update_version: | ||
| needs: update_release_draft | ||
| if: ${{ needs.update_release_draft.outputs.skip_job != 'true' }} |
Copilot
AI
Apr 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] Ensure the 'skip_job' output is always a string, as intended, to guarantee reliable comparison; consider coercing the output if necessary.
| if: ${{ needs.update_release_draft.outputs.skip_job != 'true' }} | |
| if: ${{ needs.update_release_draft.outputs.skip_job != "\"true\"" }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Logical type comparisons do not need to be enclosed in double quotes, so we will leave it as it is.
Co-authored-by: Copilot <[email protected]>
Before publishing the release notes, the task of merging the update PR for
CHANGELOG.mdneeds to be completed.During this process, not only will gradle.properties be updated to the release version, but the version specified in the log settings will also be updated to match the release version. This ensures that all files are updated to the same version as gradle.properties when setting the release draft or preparing the next development version after the release.