diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1fd07a8..25fa89a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -84,6 +84,12 @@ the pull request so the next release gets the right version. Renovate merges minor, patch and digest updates by itself once the checks pass. Major updates and proto updates wait for a maintainer. +Once a week Renovate also refreshes `Cargo.lock` within the ranges the +manifests allow and merges that the same way. An indirect dependency has no +line in a manifest, so this refresh is how a fix in one arrives. The lock +file is the repository's own: a function that depends on the SDK resolves +its dependencies itself. + A new version of `prost-build`, `tonic-prost-build` or `pbjson-build` can change the generated code, and its pull request then fails `codegen-drift`. Check out the branch, run `cargo run -p codegen`, and push the result to the diff --git a/renovate.json b/renovate.json index 2bd76ba..b1d1c49 100644 --- a/renovate.json +++ b/renovate.json @@ -1,6 +1,7 @@ { "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": ["config:recommended", "docker:pinDigests", "helpers:pinGitHubActionDigests"], + "lockFileMaintenance": { "enabled": true }, "packageRules": [ { "description": "Update the example function's build and runtime images in one PR", @@ -9,8 +10,8 @@ "groupName": "example function images" }, { - "description": "Automerge non-major updates and digest pins once CI passes", - "matchUpdateTypes": ["minor", "patch", "digest", "pin", "pinDigest"], + "description": "Automerge non-major updates, digest pins and lock file maintenance once CI passes", + "matchUpdateTypes": ["minor", "patch", "digest", "pin", "pinDigest", "lockFileMaintenance"], "automerge": true }, {