oxidecomputer / oxidecomputer/progenitor
Automate infrastructure for cutting releases
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 136
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
It would be really nice if we had automated infra that would let someone push a tag, then automatically cut a release and push to crates.io based on that.
I've used this pattern before, which involves providing a CARGO_REGISTRY_TOKEN as an environment secret.
https://github.com/oxidecomputer/cancel-safe-futures/blob/main/.github/workflows/release.yml
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced .github/workflows/release.yml workflow and comparing its tag, release, and crates.io publishing steps with this repository. Confirm how CARGO_REGISTRY_TOKEN would be provided as an environment secret and which tag pattern should trigger the process. Done means pushing the agreed tag automatically creates a release and publishes the crate to crates.io.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100