Repository navigation
ci: pin the recorder image's base images by digest - #384
Merged
Merged
Conversation
The Dockerfile named node:20-alpine and python:3.12-slim by tag, and a tag can be moved to other content after the fact. Those were the only two container dependencies in the repo, and OpenSSF Scorecard's Pinned-Dependencies check counted 0 of 2 pinned. The workflows have pinned their actions by SHA for this reason already; the image had been missed. A digest that never moves also stops receiving the base image's security fixes, so Dependabot now watches the Dockerfile. It is told to ignore minor and major version updates, because which Node and Python the image runs is a decision, and CI tests 3.12. The fingerprint is unchanged. The image was not built: no CI job builds it and this machine has no Docker. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The Dockerfile named
node:20-alpineandpython:3.12-slimby tag, and a tag can be moved to other content after the fact. Scorecard's Pinned-Dependencies check counted 0 of 2 container images pinned.apps/orchestrator/Dockerfile: both base images pinned by digest, keeping the tag for readability..github/dependabot.yml: adockerentry so the digests keep moving, on the same Monday schedule as the others. Minor and major version updates are ignored: which Node and Python the image runs is a decision, and CI tests 3.12.Checked
test_container_and_legacy_runtime.pypasses (6 passed), anddependabot.ymlparses as YAML.15846a0915769d4a. No frozen file is touched.Not checked
docker build.ignorerule still lets digest-only bumps through. The first Monday run will show it; if no digest PR ever arrives, that rule needs another look.This does not bring Pinned-Dependencies to 10: 8
pipcommands remain unpinned, in the Dockerfile and the workflows.🤖 Generated with Claude Code