Release v0.4.2 - #17
Merged
Merged
Conversation
[skip ci] Manual repair: CI run 31701259508 published 0.4.2 to Maven Central but crashed on a transient Sonatype 502 before committing/tagging. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
DRMacIver
enabled auto-merge
August 17, 2026 10:28
The tagged release commit's message carries the CI-skip marker (so that its push to main would not retrigger CI), which also suppressed all PR checks; this merge gives the PR a head commit without it.
DRMacIver
force-pushed
the
release/v0.4.2
branch
from
August 17, 2026 10:31
a47a73f to
51ded13
Compare
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.
Lands the v0.4.2 release bookkeeping on main. The release itself is fully out — Maven Central publish, the
v0.4.2tag (which points at this branch's commit), and the GitHub release all exist — but the corresponding commit (version bump, changelog entry,RELEASE.mdremoval) never made it to main:RELEASE.mdstill on main) correctly recovered from the duplicate-version deploy failure via the new logic from Recover the release when mvn deploy fails after the Central upload #16, but then failed pushing thev0.4.2tag, which by then already existed.This is the
push-or-prfallback done by hand: merging it removesRELEASE.mdfrom main and aligns the pom at 0.4.2, so subsequent merges to main stop attempting to re-release 0.4.2.🤖 Generated with Claude Code