Publish to the Gitea Maven registry (0.2.0) #8

Merged
mi merged 2 commits from publish-registry into main 2026-10-01 16:49:41 +02:00
Owner

Pulled forward before step 7 so hsadmin-ng can consume werkcrappit.

  • Both modules + Gradle plugin marker → https://git.javagil.de/api/packages/mi/maven, repository configured only when GITEA_PACKAGES_TOKEN is set.
  • Version bump per PR + CHANGELOG.md, checked by VersionConsistencyTest; 0.2.0.
  • tools/publish skips a version already in the registry (Gitea refuses re-uploads), so a re-run stays green.
  • Werkator build publish: command in .werkator.yml; trigger, status context and token in the host file on mih09 (snippet in docs/publishing.md) — no branch can trigger it or read the token.

Not verifiable before merge: the upload itself; the first publish build after the merge shows it.

CI on werkator.javagil.de: green (75 s).

PR-doc: docs/prs/2026-10-01-PR#8-publish-registry.md

🤖 Generated with Claude Code

Pulled forward before step 7 so hsadmin-ng can consume werkcrappit. - Both modules + Gradle plugin marker → `https://git.javagil.de/api/packages/mi/maven`, repository configured only when `GITEA_PACKAGES_TOKEN` is set. - Version bump per PR + `CHANGELOG.md`, checked by `VersionConsistencyTest`; 0.2.0. - `tools/publish` skips a version already in the registry (Gitea refuses re-uploads), so a re-run stays green. - Werkator build `publish`: command in `.werkator.yml`; trigger, status context and token in the host file on mih09 (snippet in `docs/publishing.md`) — no branch can trigger it or read the token. Not verifiable before merge: the upload itself; the first `publish` build after the merge shows it. CI on werkator.javagil.de: green (75 s). PR-doc: `docs/prs/2026-10-01-PR#8-publish-registry.md` 🤖 Generated with [Claude Code](https://claude.com/claude-code)
mi added 2 commits 2026-10-01 16:48:48 +02:00
Both modules and the Gradle plugin marker go to the Maven registry of
git.javagil.de. Every PR bumps the version and adds a CHANGELOG entry,
checked by VersionConsistencyTest; tools/publish skips a version that is
already there, so re-running a main build stays green. The Werkator
build "publish" is split like Werkator's own deployment: the command in
the repository, trigger and token in the host's configuration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mi merged commit 15110d2475 into main 2026-10-01 16:49:41 +02:00
mi deleted branch publish-registry 2026-10-01 16:49:41 +02:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mi/werkcrappit#8