Sign the Maven Central upload, and probe the forge registry before publishing #14
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/scalatags-webawesome!14
Loading…
Reference in a new issue
No description provided.
Delete branch "wip/publish-pgp-passphrase"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The v3.12.0 tag run (run 775) published 3.12.0 to the forge Maven registry and then failed in the Maven Central step:
Mill 1.1.x reads the key from
MILL_PGP_SECRET_BASE64and its passphrase fromMILL_PGP_PASSPHRASE(both names are in the Mill jars). The step passed only the key, so the key could not be decrypted.ac93b22had removed the passphrase with the reason "key has no passphrase", which does not hold for the current key. The organisation secretMILL_PGP_PASSPHRASEexists.The registry answers 409 for a release version it already holds, and that error ends the job before the Central step. So a repeat of a tag run could never reach Central. A probe of the version POM now guards the registry step:
After the merge, the tag v3.12.0 moves to the merge commit, so that the tag run uses this workflow. The release content does not change: build.mill stays at 3.12.0. The tag run then skips the registry step, which already holds 3.12.0, and publishes to Maven Central.
🤖 Generated with Claude Code
https://claude.ai/code/session_01B4W95VNg8J3zinj28YSSRE