Repository navigation
chore(release): move main on to 1.4.0-SNAPSHOT - #248
Merged
Merged
Conversation
Step 6 of docs/RELEASE.md, after 1.3.0 was published from the v1.3.0 tag. The next line is 1.4.0, not 1.3.1: it drops the fat jars (see TODO.md). versions:set covers the four poms. README and CLAUDE.md state which version main carries and which was last released (1.4.0-SNAPSHOT / 1.3.0), and CLAUDE.md's paragraph about main sitting at a plain release version describes a window that has closed again. The consumer-facing dependency snippets stay at 1.3.0, SECURITY.md stays at 1.3.x, and [Unreleased] already compares v1.3.0...HEAD. mvn validate resolves the reactor at the new version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuAkLtHrCTx81vP5Mt4jad
1.3.0 is the last release with fat jars on the GitHub release. They were never on Central: the assembly is <attach>false</attach>, the Central bundle is collected with --maven-only, and no file rule in release-assets.json sets "central": true. The item now lists what goes with them instead of asking whether to. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuAkLtHrCTx81vP5Mt4jad
bernardladenthin
had a problem deploying
to
maven-central
October 26, 2026 20:56 — with 
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
startgate
October 26, 2026 20:56 — with
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
October 26, 2026 20:56 — with
GitHub Actions
Failure
GitHub Actions
Failure
|
Caution Review failedThe pull request is closed. Finishing Touches
Comment |
|
7 of 10 tasks
This branch had an error being deployed
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.
Summary
docs/RELEASE.md: after the 1.3.0 release,versions:setmoves the four poms to1.4.0-SNAPSHOT. The next version is 1.4.0, not 1.3.1, because 1.4.0 drops the fat jars.1.4.0-SNAPSHOTand the last release is1.3.0. CLAUDE.md's paragraph about main being on a plain release version described a window that has closed again.1.3.0,SECURITY.mdstays at 1.3.x, and[Unreleased]in CHANGELOG already comparesv1.3.0...HEAD.<attach>false</attach>, the Central bundle is collected with--maven-only, and no rule inrelease-assets.jsonsets"central": true. The item now lists everything that goes with them.Test plan
mvn validateresolves the reactor at1.4.0-SNAPSHOT.v1.3.0) is green: Central accepted deployment0518820c-9024-481a-9775-ed294060780e, and the GitHub release has 56 assets.Related issues / PRs
Refs #247
Checklist
🤖 Generated with Claude Code
https://claude.ai/code/session_01DuAkLtHrCTx81vP5Mt4jad