Update github.com/bufbuild/protoplugin digest to 25d1d28#220
Update github.com/bufbuild/protoplugin digest to 25d1d28#220renovate[bot] wants to merge 6 commits intomainfrom
Conversation
| github.com/bufbuild/protoplugin v0.0.0-20250218205857-750e09ce93e1 h1:V1xulAoqLqVg44rY97xOR+mQpD2N+GzhMHVwJ030WEU= | ||
| github.com/bufbuild/protoplugin v0.0.0-20250218205857-750e09ce93e1/go.mod h1:c5D8gWRIZ2HLWO3gXYTtUfw/hbJyD8xikv2ooPxnklQ= |
There was a problem hiding this comment.
These would be removed by a go mod tidy. Feels like:
a. renovate should do this itself...
b. we ought to have caught this in CI with a checkgenerate step or similar
Shouldn't be very expensive. Signed-off-by: Stefan VanBuren <svanburen@buf.build>
* Rename inner job to `ci` rather than `build` * Reorganize steps so longest bits run last (fail fast) * Add `persist-credentials: false` to actions/checkout to appease zizmor Signed-off-by: Stefan VanBuren <svanburen@buf.build>
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Seems like the `go run` version isn't caching build artifacts...? Signed-off-by: Stefan VanBuren <svanburen@buf.build>
e60ec46 to
90e53e9
Compare
Signed-off-by: Stefan VanBuren <svanburen@buf.build>
To actually fix the issue. Signed-off-by: Stefan VanBuren <svanburen@buf.build>
|
@anuraaga might be best to review commit-by-commit, but since I noticed the |
This PR contains the following updates:
750e09c→25d1d28Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.