GRI-2187: tag-triggered release workflow for the forge registry #3

Merged
vivy merged 2 commits from feature/GRI-2187-release-publish into dev 2026-11-17 14:54:46 +00:00
Member

Summary

  • Remaining scope from GRI-2187 after #2 landed: actual cargo publish 0.1.0 needs a forge token with write:package scope, which my agent token does not have.
  • Adds .github/workflows/release.yml: on a v* tag push it runs cargo publish --registry grimoirix -p grimoirix-server, authenticated via the repository secret CARGO_REGISTRY_TOKEN. This moves the credential need from "an agent's personal token" to "a repository secret someone with package-admin rights configures once" — a release then needs only a tag push, not a manual publish.
  • Updates the README's "Release it" section to describe the automated path, keeping the manual cargo publish command as a documented fallback.

Still needed from someone with forge package-admin rights

  1. Create a forge token with write:package scope and store it as the CARGO_REGISTRY_TOKEN secret on this repository.
  2. Push tag v0.1.0 on the current dev tip (crates/grimoirix-server/Cargo.toml is already at 0.1.0) — that tag push is what fires the publish.

Test plan

  • scripts/local-gates.sh (fmt, clippy -D warnings, test incl. doc tests, cargo deny) — all green, unchanged by this diff since it touches only workflow/README.
  • Cannot verify the publish step itself without the write:package-scoped token/secret above.
## Summary - Remaining scope from GRI-2187 after #2 landed: actual `cargo publish 0.1.0` needs a forge token with `write:package` scope, which my agent token does not have. - Adds `.github/workflows/release.yml`: on a `v*` tag push it runs `cargo publish --registry grimoirix -p grimoirix-server`, authenticated via the repository secret `CARGO_REGISTRY_TOKEN`. This moves the credential need from "an agent's personal token" to "a repository secret someone with package-admin rights configures once" — a release then needs only a tag push, not a manual publish. - Updates the README's "Release it" section to describe the automated path, keeping the manual `cargo publish` command as a documented fallback. ## Still needed from someone with forge package-admin rights 1. Create a forge token with `write:package` scope and store it as the `CARGO_REGISTRY_TOKEN` secret on this repository. 2. Push tag `v0.1.0` on the current `dev` tip (`crates/grimoirix-server/Cargo.toml` is already at `0.1.0`) — that tag push is what fires the publish. ## Test plan - [x] `scripts/local-gates.sh` (fmt, clippy -D warnings, test incl. doc tests, cargo deny) — all green, unchanged by this diff since it touches only workflow/README. - [ ] Cannot verify the publish step itself without the `write:package`-scoped token/secret above.
GRI-2187: add tag-triggered release workflow for the forge registry
Some checks failed
CI / cargo deny (pull_request) Failing after 2m29s
CI / cargo fmt (pull_request) Successful in 4s
CI / cargo clippy (pull_request) Successful in 55s
CI / cargo test (pull_request) Successful in 1m0s
556f17ede5
GRI-2187: retrigger CI (cargo deny failed on a toolchain download timeout, not a code issue)
All checks were successful
CI / cargo fmt (pull_request) Successful in 8s
CI / cargo clippy (pull_request) Successful in 1m5s
CI / cargo test (pull_request) Successful in 59s
CI / cargo deny (pull_request) Successful in 1m14s
c456724038
vivy merged commit d564e1ef10 into dev 2026-11-17 14:54:46 +00:00
vivy deleted branch feature/GRI-2187-release-publish 2026-11-17 14:54:47 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoirix-backend-libs!3
No description provided.