docs: document tag-driven plugin releases - #25
Merged
Merged
Conversation
This was referenced Sep 22, 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
1 participant
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.
Plugin releases no longer require a numeric version-bump commit. Document tags as the release-version source,
main-SNAPSHOTas the local marker, PR-only development artifacts, and verification on default-branch pushes. Dependency and build-tool versions stay pinned; archived plugins retain their existing workflows.Validation: five documentation checker tests passed; 678 local links and anchors across 187 Markdown pages and project navigation passed. Companion workflow changes cover all 32 active Maven plugins.
Companion plugin PRs (32)