build: roll back ggshield to v1.53.0 - #2
Merged
Merged
Conversation
1.54.0 ships a broken certificate bundle, reported to the ggshield team. Until a fixed release lands, every sandbox the kit builds gets a scanner whose TLS verification cannot be trusted, which is a poor foundation for a kit whose entire job is to sit on the agent's output path. Pin GGSHIELD_VERSION and both per-arch SHA256 back to 1.53.0. The digests were re-derived by downloading the published release tarballs and running sha256sum, not copied from the notes of the commit that bumped them. The cost of the rollback is the Mistral Vibe hook: 1.53.0 enumerates claude-code, codex, copilot, cursor and vscode, and vibe only arrived in 1.54.0. The README and the Docker Hub overview stop promising it. Nothing else in the install step changes - asset naming, archive layout and the symlink are identical across the two versions. The pin now carries a comment naming the certificate-bundle issue, so the next person to bump does not walk straight back into it. Verified end to end: sbx kit validate passes, sbx create applies both gitguardian install steps (so the checksum check passed against the real download), and inside the sandbox ggshield reports 1.53.0 with machine doctor showing AI hooks installed for Claude Code, Codex, Copilot CLI and Cursor.
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
1 participant
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.
Problem
ggshield 1.54.0 ships a broken certificate bundle. The issue is already logged with the ggshield team. Until a fixed release lands, every sandbox this kit builds gets a scanner whose TLS verification cannot be trusted — a poor foundation for a kit whose whole job is to sit on the agent's authorized output path.
Change
GGSHIELD_VERSIONand both per-archSHA256pins go back to 1.53.0. The digests were re-derived by downloading the published release tarballs and runningsha256sum, not copied from the notes of the commit that bumped them:x86_64-unknown-linux-gnu→234d1a62ea7b769695c7e5aee8f29e9d0069cd09b4e5b67493d3b529abb44e4aaarch64-unknown-linux-gnu→097616513fe7a4f25831a464b8968b124af32d274e2ce006e388800605696b20README.md,docs/dockerhub-overview.md).Cost of the rollback
Mistral Vibe loses its AI hook. Probing the 1.53.0 binary directly, it enumerates
claude-code,codex,copilot,cursor,vscode—vibeonly arrived in 1.54.0. Nothing else in the install step differs: asset naming, archive layout and the/usr/local/binsymlink are identical across the two versions.Verification
sbx kit validate .→ VALIDsbx createfrom the local kit — bothgitguardianinstall steps pass, so the checksum check succeeded against the real downloadggshield, version 1.53.0ggshield machine doctor→✓ Authentication — token reaches GitGuardian,✓ AI hooks — installed for: Claude Code, Codex, Copilot CLI, CursorThe remaining
machine doctorfailures are by design: git hooks (the kit passes--no-git-hooks) and thehoneytokens:write/ai-discover:sendscopes, which the README deliberately leaves out of a scan-only token.