oxidecomputer / oxidecomputer/omicron
Make renovate work with cargo-hakari
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
The workspace-hack package results in two issues with dependabot:
- For some updates, the workspace-hack would need to be regenerated. A workaround is to fetch the branch locally, then run
cargo hakari generateand push it to the branch. - Dependabot will try and do updates to crates that are only referred to in workspace-hack.
We can solve both these issues with Renovate's support for excluding particular paths, and running post-upgrade commands.
Useful links:
- https://github.com/renovatebot/github-action for self-hosted Renovate (required for post-upgrade commands)
- https://docs.renovatebot.com/configuration-options/#postupgradetasks where we can run hakari after upgrades and before commits
- https://docs.renovatebot.com/configuration-options/#ignorepaths where we can exclude workspace-hack
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 by reviewing the repository's existing dependency automation and the linked Renovate GitHub Action, post-upgrade task, and ignorePaths documentation. Confirm how cargo-hakari generates workspace-hack and which crates it references. Done means Renovate can update dependencies, regenerate workspace-hack before committing, and avoid updating crates referenced only there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100