Repository navigation
chore(release): 1.3.0 - #247
Merged
Merged
Conversation
Step 1 of docs/RELEASE.md. versions:set moves the four poms (and their outputTimestamp); the rest is the hand-maintained list: - README.md and srcmorph-maven-plugin/README.md: the three dependency/plugin snippets and the "Current reactor version" line. - CLAUDE.md: reactor version, layout block, the fat-jar command, and the paragraph about main sitting at a plain release version until the tag. - SECURITY.md: 1.3.x is the current line, 1.2.x and older are not patched. - CHANGELOG.md: [Unreleased] becomes [1.3.0] - 2026-10-26, footer links added. - examples/windows-fatjar/pom.xml: srcmorph.version 1.3.0 and the central-snapshots repository removed, as its comment asked; the matching note in docs/windows-intel-core-ultra.md goes with it. The example is not released; users build it locally. Built once against the 1.3.0-SNAPSHOT from Publish run 40367427445 with an empty local repository: resolved from Central, 32 MiB jar. - TODO.md: the open item is now the same check against 1.3.0 after the release. Headings, footer links and tags agree except v1.3.0, which is cut after the merge. mvn validate passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuAkLtHrCTx81vP5Mt4jad
bernardladenthin
had a problem deploying
to
startgate
October 26, 2026 20:07 — with
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
October 26, 2026 20:07 — with
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
maven-central
October 26, 2026 20:07 — with
GitHub Actions
Failure
|
This was referenced Oct 26, 2026
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: the reactor moves from1.3.0-SNAPSHOTto1.3.0.versions:setbumps all four poms in lockstep.README.md,srcmorph-maven-plugin/README.md,CLAUDE.md, andSECURITY.md, where 1.3.x becomes the current line.CHANGELOG.md:[Unreleased]becomes[1.3.0] - 2026-10-26, and the footer gets a link for 1.3.0.examples/windows-fatjar/pom.xml:srcmorph.versionis set to1.3.0and thecentral-snapshotsrepository is removed. The example itself is not released; users build it locally.Test plan
mvn validateresolves the reactor at 1.3.0.v1.3.0is missing, because the tag is cut after the merge.1.3.0-SNAPSHOTfrom Publish run 40367427445, with an empty local repository and Central only. It resolved and produced a 32 MiB jar. The same check against 1.3.0 is aTODO.mditem for after the release.Related issues / PRs
Refs #244, #246
After the merge (owner)
v1.3.0tag and checkpublish_to_central.https://repo1.maven.org/maven2/net/ladenthin/<artifact>/1.3.0/, and thecentral-releasejob must print the Portal deployment id.mainto1.3.1-SNAPSHOT.Checklist
🤖 Generated with Claude Code
https://claude.ai/code/session_01DuAkLtHrCTx81vP5Mt4jad