Release 3.12.0 #13
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!13
Loading…
Reference in a new issue
No description provided.
Delete branch "release/3.12.0"
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?
Sets the library version to 3.12.0 and dates the 3.12.0 entry in CHANGELOG.md.
After the merge, tag v3.12.0 on the merge commit (the precedent of v3.2.1 and v3.2.1.1). The tag publishes to the Forgejo Maven registry and to Maven Central.
🤖 Generated with Claude Code
https://claude.ai/code/session_01B4W95VNg8J3zinj28YSSRE
Added
b736fc6, which changes the publish flow from #11.Problem found before the merge: this PR puts the release version 3.12.0 on
main. The run for that push publishes 3.12.0 to the forge Maven registry. Thev3.12.0tag run then uploads the same version again, and the registry answers 409 ("You cannot publish a package if a package of the same name and version already exists", forgejo/routers/api/packages/maven/maven.go:379). That step fails, so the Maven Central step after it never runs.Fix: the forge step now has
if: github.ref_type == 'tag' || endsWith(steps.version.outputs.value, '-SNAPSHOT'), with a new step that readswebawesome.jvm.publishVersion. A push to main publishes a snapshot as before. A release version waits for its tag, and the tag run publishes it to the forge registry and to Maven Central.Also dates the 3.12.0 changelog entry to 2026-09-12.