Repository navigation
release: 0.7.1 — the quickstart points at images that ship neither the CA bundle with compromised intermediates nor the slow trace-header parser - #19
Merged
Conversation
…e CA bundle with compromised intermediates nor the slow trace-header parser The six image lines move from 0.7.0 to 0.7.1, pinned by the OCI index digests GHCR serves for the tags, read anonymously after the release run for the tag finished green on every job; :latest carries the same four. The file's own comment says why it cannot point at an older tag. Run the way a stranger does before this commit, from an empty directory holding only the compose file and scripts/demo.sh: the compose pulled by digest, the boards answered, demo.sh ran all nine steps on the rehearsal adapter and exited 0, and down -v removed it. Read back from the running images: the pipe and the judge carry certifi 2026.10.19, opentelemetry-api 1.45.1 and fastapi 0.161.1, the investigator opentelemetry-api 1.45.1; no image trusts the root PYSEC-2026-4320 names, in certifi's bundle, the system store or Node's built-in roots.
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
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 quickstart's six image lines move from 0.7.0 to 0.7.1, pinned by digest as
docs/releasing.mdsays. The digests are the OCI index digests GHCR serves for the0.7.1tags, read anonymously after the release run for the tag finished green on every job;:latestcarries the same four.0.7.1 is a patch release: certifi 2026.10.19 and opentelemetry-api 1.45.1 for two advisories, fastapi 0.161.1 and ruff 0.17.1 (#18), and the demo's token fix (#14). The file's own comment now says why it cannot point at an older tag: 0.7.1 is the first whose images ship neither a CA bundle that trusts compromised intermediates nor a trace-header parser one request could keep busy for seconds.
Run the way a stranger does before this was opened, from an empty directory holding only the compose file and
scripts/demo.sh: the compose pulled all four images by digest, the three boards answered200within seconds, anddemo.shran all nine steps on the rehearsal adapter, from the ai route to the recovery that verified the approved work.demo exit=0;down -vremoved the containers, the volumes and the network.Read back from the running images: the pipe and the judge carry certifi 2026.10.19, opentelemetry-api 1.45.1 and fastapi 0.161.1; the investigator carries opentelemetry-api 1.45.1. No image trusts the root PYSEC-2026-4320 names: not certifi's bundle, not the system store (Debian in the three services, Alpine in the bridge), not Node's built-in roots in the investigator and the bridge.
A correction to the tag's note. It says every service's outbound HTTPS went through certifi. Read back from the images, only the pipe and the judge carry certifi: the investigator's Python has no HTTP client library and verifies against the system store, and the bridge has no certifi either. The investigator's lock lists certifi because its development venv does. The tag stays where it is; this is the record.
Gate: STACK GATE GREEN locally; CI read back before merging.