ci: publish to the forge Maven registry; fix pom repo name #11

Merged

mph merged 1 commit from forge/publish into main

2026-07-28 17:24:39 +00:00

mph commented

2026-07-28 11:44:14 +00:00

Owner

Summary

scalatags-webawesome now lives on the forge. This wires publishing to match the other first-party libraries (claude-code-query, iw-support):

Add the iterative-works Forgejo Maven registry as an additional publish target via MavenPublishModule/publishAll. Every push to main publishes the current -SNAPSHOT; a v* tag publishes the release. Uses org-level MILL_MAVEN_* secrets (basic-auth, no PGP).
Keep Maven Central (PGP via SonatypeCentralPublishModule) for tag releases only — Central stays primary for this public library; the forge is the additional target.
Gate publishing on ./mill __.test (the previous workflow published without running tests).
Fix the pom url/versionControl, which pointed at the nonexistent scalatags-web-awesome repo, to scalatags-webawesome (matches the git repo and artifactName).

Notes

Registry read is anonymous (org is public); publishing this public library there leaks nothing (it is already on Central).
The Sonatype/PGP secrets are already provisioned as forge org secrets, so the tag→Central path needs no new setup.
CI (compile/format/lint/test) is unchanged and already ubuntu-latest; the test job runs the Scala.js utest suite, which needs Node.js in the runner — this PR's CI run is the first validation of that on the forge runner.

🤖 Generated with Claude Code

## Summary `scalatags-webawesome` now lives on the forge. This wires publishing to match the other first-party libraries (claude-code-query, iw-support): - **Add the iterative-works Forgejo Maven registry** as an additional publish target via `MavenPublishModule/publishAll`. Every push to `main` publishes the current `-SNAPSHOT`; a `v*` tag publishes the release. Uses org-level `MILL_MAVEN_*` secrets (basic-auth, no PGP). - **Keep Maven Central** (PGP via `SonatypeCentralPublishModule`) for tag releases only — Central stays primary for this public library; the forge is the additional target. - **Gate publishing on `./mill __.test`** (the previous workflow published without running tests). - **Fix the pom `url`/`versionControl`**, which pointed at the nonexistent `scalatags-web-awesome` repo, to `scalatags-webawesome` (matches the git repo and `artifactName`). ## Notes - Registry read is anonymous (org is public); publishing this public library there leaks nothing (it is already on Central). - The Sonatype/PGP secrets are already provisioned as forge org secrets, so the tag→Central path needs no new setup. - CI (`compile`/`format`/`lint`/`test`) is unchanged and already `ubuntu-latest`; the `test` job runs the Scala.js utest suite, which needs Node.js in the runner — this PR's CI run is the first validation of that on the forge runner. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

mph added 1 commit

2026-07-28 11:44:15 +00:00

ci: publish to the forge Maven registry; fix pom repo name

CI / format (pull_request) Successful in 48s

Details

CI / compile (pull_request) Successful in 52s

Details

CI / lint (pull_request) Successful in 50s

Details

CI / test (pull_request) Successful in 46s

Details

8f6da81f3f

Add the iterative-works Forgejo Maven registry as an additional publish
target (every push publishes the SNAPSHOT; tags publish the release),
gated on unit tests, while keeping Maven Central (PGP) for tag releases.
Fix the pom url/versionControl, which pointed at the nonexistent
scalatags-web-awesome repo, to scalatags-webawesome.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

mph merged commit 5a2dec45da into main

2026-07-28 17:24:39 +00:00

mph referenced this pull request from a commit

2026-07-28 17:24:40 +00:00

Merge pull request 'ci: publish to the forge Maven registry; fix pom repo name' (#11) from forge/publish into main

mph deleted branch forge/publish

2026-07-28 17:24:43 +00:00