Skip to content

ci: publish releases from release.yml through crates.io trusted publishing - #5

Merged
GeneralPawz merged 1 commit into
mainfrom
ci/release-workflow
Oct 28, 2026
Merged

GeneralPawz merged 1 commit into
mainfrom
ci/release-workflow

Conversation

@GeneralPawz

Copy link
Copy Markdown
Contributor

The crates are accepted by crates.io only through trusted publishing (token publishing returns 403). The configured publisher expects workflow release.yml in the crates.io environment of openbimrs/bsdd.

This adds that workflow, modelled on the hardened openbimrs/idm one: on a v<version> tag it checks the tag is on main and matches the manifest and changelog, runs scripts/gate.sh, publishes through rust-lang/crates-io-auth-action (skipping versions already live, so reruns are safe) and creates the GitHub release from the changelog section. CONTRIBUTING (and AGENTS where relevant) now describe it instead of manual publishing. Manual dispatch rehearses gate-only.

…shing

The crates are accepted by crates.io only through trusted publishing; token publishing returns 403. The configured publisher expects repository openbimrs/bsdd, workflow release.yml and environment crates.io. A v<version> tag now gates the tagged commit with scripts/gate.sh, publishes what is not yet live, and creates the GitHub release from the changelog section.
@GeneralPawz
GeneralPawz merged commit 8f4f17a into main Oct 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant