chore(docker): sync toolchain pin to development's gRPC 1.83.2 recipe - #1312
Merged
Merged
Conversation
`development` carries c32e611 (gRPC 1.83.2), a toolchain-key input that `main` does not have yet, so the toolchain pin propagated into `development` by #1307 (caddy-crowdsec-1efe7f19fa52a512 @ sha256:6575f4c6…, computed for main's gRPC 1.83.1 recipe) is stale here: the recipe on this branch recomputes to caddy-crowdsec-9eb9862f44b9e769, failing verify-toolchain-pin. Bumps the two ARG lines to the key/digest that match development's recipe. This is the manual equivalent of the daily open-bump-pr bot (now using the chore(docker): convention). Verified on this branch: - scripts/toolchain-key.sh -> caddy-crowdsec-9eb9862f44b9e769 - imagetools inspect <that tag> -> sha256:b41e571d5951bbfc3daa3dccdca033ad9dee535a8e720ac7e3b0bce338f223b2 Claude-Session: https://claude.ai/code/session_01KXA4x9LrA2AsnLrvdHMZbS
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
Contributor
✅ Supply Chain Verification Results✅ PASSED 📦 SBOM Summary
🔍 Vulnerability Scan
📎 Artifacts
Generated by Supply Chain Verification workflow • View Details |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bumps the two toolchain-pin
ARGlines inDockerfileondevelopment:CHARON_TOOLCHAIN_TAGcaddy-crowdsec-1efe7f19fa52a512caddy-crowdsec-9eb9862f44b9e769CHARON_TOOLCHAIN_DIGESTsha256:6575f4c6…f8f00sha256:b41e571d5951bbfc3daa3dccdca033ad9dee535a8e720ac7e3b0bce338f223b2Why
developmentcarriesc32e611a(gRPC 1.83.2) — a toolchain-key input thatmaindoes not have yet. The pin that propagation PR #1307 brought frommainwas computed for
main's gRPC-1.83.1 recipe (…1efe7f19…). Ondevelopment'srecipe the key recomputes to
…9eb9862f…, soverify-toolchain-pinis red ondevelopmentuntil the pin is synced.This is the manual equivalent of the daily
open-bump-prbot (now using thechore(docker):convention, per the change in #1308). Supersedes bot PR#1310, which is being closed.
Verification (on this branch)
bash scripts/toolchain-key.sh→caddy-crowdsec-9eb9862f44b9e769✅docker buildx imagetools inspect ghcr.io/wikid82/charon-toolchain:caddy-crowdsec-9eb9862f44b9e769→sha256:b41e571d5951bbfc3daa3dccdca033ad9dee535a8e720ac7e3b0bce338f223b2✅Base
development. Do not merge before CI is green.