chore: prepare workflows for 3.x line - #5341
Merged
Merged
Conversation
djankows
approved these changes
Oct 1, 2026
This file contains hidden or 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
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.
Pull Request
Workflow changes
codeql-analysis.yml: Run on pushes and pull requests to3.0.0. Use a JDK 17 Maven cache key. The scheduled scan remains in the file; GitHub runs scheduled workflows from the default branch.maven.yml: Run the build and snapshot deployment workflow on pushes to3.0.0. Rename the workflow toBuild Test Deploy 3.0.0. The existing Java 17, 21, and 25 build matrix remains, with snapshot deployment on Java 17.prepare-release.yml: Set the prepare-release pull request base to the branch selected for the manual run. The workflow now uses that branch instead of an implicit default base.release.yml: Check out the branch selected for the manual run after publishing Javadocs. Create the next-snapshot pull request against that branch. Remove the steps that update the1.5README and the 2.x Wiki.maven-v1.ymlandmaven-v1-pulls.yml: Remove the 1.5 push and pull request workflows from the3.0.0branch. The1.5branch has its own copies.Script changes
CI/lastRelease.py: Find the latest published v3 release. If none exists, use the latest published v2 release and print a warning.CI/releaseNotes.py: List pull requests merged into3.0.0and create the draft GitHub release from that branch.CI/publishRelease.py: Publish the GitHub release with3.0.0as its target branch.CI/prepare-release.sh: Update dependency examples in the main README and plugin READMEs to the new release version. Remove the old step that added a release row to the main README.CI/post-release.sh: Stop copying the scripts for 1.5 README and 2.x Wiki updates. The release workflow no longer runs them.CI/update-v1-readme.shandCI/update-wiki.sh: Remove these scripts from the3.0.0branch because its release does not update the 1.5 README or the 2.x Wiki.CI/test.py: Remove an unused copy of the release notes script.Documentation
Type of Change
Checklist
Screenshots / Additional Context