Bump reactor version to 1.1.1 for the release retry#147
Merged
Conversation
The first v1.1.0 release attempt failed Sonatype Central's deployment validation (missing sources-jar signatures, fixed in the prior commit) before anything went public - no artifacts were actually published under 1.1.0. Rather than force-move the protected v1.1.0 git tag (GitHub rejects it with a 403; confirmed directly), bump to 1.1.1 for a clean retry with a brand-new tag. `mvn versions:set -DnewVersion=1.1.1 -Dexcludes=net.ladenthin:llamacpp-ai-index-maven-plugin` for the three real modules; the relocation stub's own <version> stays pinned at 1.0.4 (its <parent><version> correctly tracks 1.1.1), and its <relocation><version> target updated to 1.1.1 by hand (not touched by versions:set). Swept README.md/CLAUDE.md/TODO.md/CHANGELOG.md/ srcmorph-maven-plugin/README.md/examples' illustrative jar-name comments for the same bump, preserving the unrelated keepachangelog.com spec- version links. CHANGELOG's former [Unreleased] section is now [1.1.1], since 1.1.0 was never actually released, plus a new Fixed entry documenting the sources-jar signing bug.
bernardladenthin
had a problem deploying
to
maven-central
July 15, 2026 22:37 — with 
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
maven-central
July 15, 2026 22:37 — with
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
startgate
July 15, 2026 22:37 — with
GitHub Actions
Error
GitHub Actions
Error
7 tasks
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
2 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
v1.1.0release attempt failed Sonatype Central's deployment validation (missing sources-jar signatures, fixed by Fix sources-jar signing: attach-sources ran after gpg:sign, not before #146) before anything actually went public — nothing was published under1.1.0.v1.1.0git tag is protected (force-push to a different commit was rejected with403 Forbidden), so rather than fight that protection, this bumps to1.1.1for a clean retry with a brand-new tag.mvn versions:set -DnewVersion=1.1.1 -Dexcludes=net.ladenthin:llamacpp-ai-index-maven-pluginfor the three real modules (srcmorph,srcmorph-cli,srcmorph-maven-plugin). The relocation stub's own<version>stays pinned at1.0.4(its<parent><version>correctly tracks the new1.1.1), and its<relocation><version>target was updated to1.1.1by hand (not a project/parent version reference, soversions:setdoesn't touch it).README.md/CLAUDE.md/TODO.md/CHANGELOG.md/srcmorph-maven-plugin/README.md/theexamples/launcher scripts' illustrative jar-name comments for the same version bump — preserving the unrelatedkeepachangelog.comspec-version links, which happen to also read1.1.0.CHANGELOG.md's former[Unreleased]section is now[1.1.1](since1.1.0was never actually released), plus a newFixedentry documenting the sources-jar signing bug from Fix sources-jar signing: attach-sources ran after gpg:sign, not before #146.Test plan
1.1.1via the root pom1.0.4; its<relocation>target confirmednet.ladenthin:srcmorph-maven-plugin:1.1.1mvn clean verifyfrom repo root — BUILD SUCCESSRelated issues / PRs
Follow-up to #144, #145, #146 — prepares the clean retry after the failed
v1.1.0release attempt.Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdGenerated by Claude Code