Fully enable automated releases #72
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
Most of the plugins I use fully migrated to JEP-229[^1]. It seems stable enough and reduces manual overhead when releasing the plugin. After quick chat with @lafriks in Discord, we decided to fully enable automated releases. The first part happened in #35. I followed the official docs[^2]. This will change the versioning pattern to `<amount-of-commits-on-main-branch>.v<HEAD>`. When the next release is crafted, we should add a note to the relase about this version change. I also configured Dependabot to get monthly updates for our dependencies. [^1]: https://github.com/jenkinsci/jep/blob/master/jep/229/README.adoc [^2]: https://www.jenkins.io/doc/developer/publishing/releasing-cd/ Signed-off-by: justusbunsi <[email protected]>
lafriks
approved these changes
Jun 19, 2024
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.
Most of the plugins I use fully migrated to JEP-2291. It seems stable enough and reduces manual overhead when releasing the plugin.
After quick chat with @lafriks in Discord, we decided to fully enable automated releases. The first part happened in #35. I followed the official docs2. This will eliminate the version bump PR after each release.
This will change the versioning pattern to
<amount-of-commits-on-main-branch>.v<HEAD>. When the next release is crafted, we should add a note to the release about this version change.I also configured Dependabot to get monthly updates for our dependencies.
Footnotes
https://github.com/jenkinsci/jep/blob/master/jep/229/README.adoc ↩
https://www.jenkins.io/doc/developer/publishing/releasing-cd/ ↩