Repository navigation
Pin Maven 3.9.11 in the release job so the Central bundle is accepted (Canvas 8) - #72
Merged
Merged
Conversation
… (Canvas 8) v1.11.0 published to GitHub Packages but Maven Central rejected the bundle: "Bundle has content that does NOT have a .pom file: ca/weblite/webview". The runner image had moved to a Maven whose install plugin (3.2.0) and resolver leave maven-metadata-central-staging.xml where central-publishing 0.7.0 no longer deletes it. The deploy job now installs Maven 3.9.11 (sha512-verified) before any mvn step; under it the bundle holds only the versioned directory, as for v1.10.2. Canvas 8 Operation 9 and Norms synced. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AHBmWDEnhU98pmMuZ4f9me
shannah
marked this pull request as ready for review
October 17, 2026 14:06
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.
Why
v1.11.0's release run published to GitHub Packages, but Maven Central rejected the upload:
Nothing in the release config changed between v1.10.2 and v1.11.0. The runner image's Maven did.
central-publishing-maven-plugin0.7.0 loggedPre Bundling - deleted …/ca/weblite/webview/maven-metadata-central-staging.xml.Loaded … auto-discovered prefixes). That deletion never happened, so the stray metadata file stayed in the bundle beside the versioned directory.What
.github/workflows/maven-release.yml: a new Install pinned Maven step in the deploy job..sha512.bin/first onPATHbefore anymvnstep runs./spdd-sync: a new Logic bullet in Operation 9 and a Norm explaining why the release job's Maven is pinned.Published artifacts are unchanged.
Testing
-DskipPublishing) that held onlyca/weblite/webview/1.11.0/*, and the stray metadata file was deleted. This matches v1.10.2.After merge
Tag
v1.11.1on master to publish the same code to both GitHub Packages and Central. Re-running v1.11.0 is not an option: Canvas 8 notes that neither target accepts a redeploy of an existing version.Generated by Claude Code