chore(release): move main on to 1.3.0-SNAPSHOT - #197
Merged
Conversation
Step 6 of docs/RELEASE.md, after 1.2.0 was published from the v1.2.0 tag. Leaving main on a version that already exists on Central is what the step exists to prevent: a snapshot deploy would collide, and anyone building from main would produce artifacts indistinguishable from the release. versions:set covers the four poms. The rest is the hand-maintained list that step 1 now enumerates, and the distinction matters: - README and CLAUDE.md state which version main carries and which was last released -- both moved (1.3.0-SNAPSHOT / 1.2.0). - The three consumer-facing dependency snippets stay at 1.2.0. They tell a reader what to depend on, and that is the release, never the snapshot. - CLAUDE.md's paragraph about main sitting at a plain release version with the tag not yet cut described a window that has closed; it now says a -SNAPSHOT on main is the normal state between releases. - SECURITY.md needs no change: 1.2.x is still the current release line. - CHANGELOG.md needs none either: [Unreleased] already compares v1.2.0...HEAD. mvn validate resolves the reactor at the new version.
bernardladenthin
had a problem deploying
to
maven-central
September 1, 2026 08:00 — with 
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
maven-central
September 1, 2026 08:00 — with
GitHub Actions
Failure
GitHub Actions
Failure
6 tasks
Code Review Summary✅ Overall Assessment: This PR correctly implements step 6 of the release process (docs/RELEASE.md). Review FindingsStrengths:
Verification:
Security & Quality:
This PR is ready to merge. All changes align with the documented release procedure. |
|
Coverage Report for CI Build 33484827948Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Warning No base build found for commit Coverage: 95.393%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
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
3 participants
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.
Summary
Step 6 of
docs/RELEASE.md, after 1.2.0 was published from thev1.2.0tag (run 33482292299, green).mvn versions:set -DnewVersion=1.3.0-SNAPSHOT -DgenerateBackupPoms=false— all four poms, project version and the three<parent><version>pointers.README.md/CLAUDE.md— "Current reactor version" →1.3.0-SNAPSHOT, "Last released version"1.1.1→1.2.0CLAUDE.md— the paragraph describingmainas sitting at a plain release version with the tag not yet cut described a window that has closed; it now states that a-SNAPSHOTonmainis the normal state between releasesCLAUDE.md— the localjava -jar srcmorph-cli/target/…example tracks the built artifact, so it movesSECURITY.md— no change needed,1.2.xis still the current release lineCHANGELOG.md— no change needed,[Unreleased]already comparesv1.2.0...HEADThe three consumer-facing dependency snippets deliberately stay at
1.2.0. They tell a reader what to depend on, and that is the release, never the snapshot. Same reasoning everywhere below.Test plan
mvn validateresolves the reactor at the new version (a child left pointing at a non-existent parent is the classic failure here)grep -rn "1\.1\.1" --include="*.md" .— remaining hits are deliberate history (the retired relocation stub, thellamaLibraryPathremoval note)Related issues / PRs
Follows #194, #195, #196 and the
v1.2.0release.Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdGenerated by Claude Code