GRI-2187: tag-triggered release workflow for the forge registry #3
No reviewers
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoirix-backend-libs!3
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/GRI-2187-release-publish"
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?
Summary
cargo publish 0.1.0needs a forge token withwrite:packagescope, which my agent token does not have..github/workflows/release.yml: on av*tag push it runscargo publish --registry grimoirix -p grimoirix-server, authenticated via the repository secretCARGO_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.cargo publishcommand as a documented fallback.Still needed from someone with forge package-admin rights
write:packagescope and store it as theCARGO_REGISTRY_TOKENsecret on this repository.v0.1.0on the currentdevtip (crates/grimoirix-server/Cargo.tomlis already at0.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.write:package-scoped token/secret above.