microsoft / microsoft/rust-symcrypt
Add github action to publish new version
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 15
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 11
Description
- lock to service account
- https://release-plz.dev/
- Signing off on PR is disabled for this repo, here is a work around:
cargo install release-plz locally and run release-plz update manually, then PR that change. Once it’s merged, the release-plz action is able to do the rest as though its own PR was just merged.
We should configure this after we do our major bump for static link since the new versions for rust-symcrypt and symcrypt-sys will have the workspace changes. Currently release_plz is having an issue picking up the differences.
Contributor guide
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 with the release-plz documentation and the repository's current release setup; the issue does not name any existing workflow files or tests. Configure a GitHub Action using a locked service account, accounting for the signing-off workaround and the post-major-bump workspace changes, and verify that merged release-plz changes can publish a new version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100