Repository navigation
release: 0.9.2 — the quickstart points at the same loop with the pipe and the judge on fastapi 0.162.0 - #34
Merged
Merged
Conversation
… and the judge on fastapi 0.162.0 The six image lines move from 0.9.1 to the OCI index digests GHCR serves for the 0.9.2 tags, read anonymously after the release run finished green on every job. The comment keeps saying the file needs 0.8.0 or newer and now names what moved; the investigator keeps the fastapi its own lock names. Run from an empty directory before committing: pulled by digest, the boards answered within seconds, the demo ran all nine steps with the press executed, demo exit 0, down -v clean.
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.9.1 to 0.9.2, pinned by digest as
docs/releasing.mdsays. The digests are the OCI index digests GHCR serves for the0.9.2tags, read anonymously after the release run for the tag finished green on every job;:latestcarries the same four.Nothing in 0.9.2 is something this file depends on, so its comment keeps saying it needs 0.8.0 or newer and points at the newest, now naming what moved: the pipe and the judge on fastapi 0.162.0. The one compose key added since 0.9.1 is
AWS_EC2_METADATA_DISABLEDon the work deployment's probes, which carry AWS credential files and an egress proxy; this file's investigator has neither, so there is nothing to mirror.Run the way a stranger does before this was opened, from an empty directory holding only the compose file and
scripts/demo.sh: pulled by digest, the three boards answered200within seconds, and the demo ran all nine steps (routes ai 2, reuse 1, recovery 1; the card press executed both observations; the recovery verified the 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 fastapi 0.162.0. The investigator keeps the fastapi its own lock names, 0.141.1. Dependabot proposed no bump for it; the cause is not that its floor admits the newest, since the pipe's floor did too and was raised. None of the three carries msgpack or filelock, which only the gates' tooling installs.
Rollback: re-pin these lines to the 0.9.1 digests; nothing persisted changes shape.
Gate: STACK GATE GREEN locally; CI read back before merging.