fix(ci): make publish-maven resumable with -Pskip_existing - #42
Merged
Conversation
Reposilite's releases repo refuses overwrites, so a publish run that covers any artifact a previous run already uploaded dies with 409 Conflict — which is exactly what a resumed release does. -Pskip_existing (already the default on the local release path) HEADs each POM and skips what is present, so re-running the workflow only uploads what is missing. Hit while finishing 1.27.4: the modules had landed from a partial local publish, and every matrix job then failed on the first module it re-uploaded, leaving the bundles — the artifacts that actually still needed publishing — unpublished. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Bt7RgUQ8kNZGgF4DBBUpj
THEROER
added a commit
that referenced
this pull request
Jul 31, 2026
fix(ci): make publish-maven resumable with -Pskip_existing
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
1 participant
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.
Reposilite's
releasesrepo refuses overwrites (409 Conflict), so any publish run that touches an artifact a previous run already uploaded fails — which is precisely what a resumed release is.-Pskip_existingis already the default on the local release path (releaseMaven*passes it); this brings the workflow in line.Hit while finishing 1.27.4: a partial local publish had landed the modules, so every matrix job then died on the first module it tried to re-upload, and the bundles — the artifacts that still needed publishing — never got their turn.