Repository navigation
fix(eval): refresh Nimbus freeze after mdparser change - #43
Merged
Merged
Conversation
PR #41 changed internal/infrastructure/mdparser, which is a build input of eval-supervisor, but didn't refresh eval/nimbus/v1/freeze.json. That broke the three eval CI jobs on main ("freeze.json does not match current Nimbus tree"). Regenerated with go1.26.4 and the already-audited runtime image IDs from the committed freeze. Only the mdparser input hash and the eval-supervisor static binary hash change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JAORMX
approved these changes
Oct 15, 2026
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.
Main has been red since #41 merged. The three eval jobs (offline, docker, podman) fail with
freeze.json does not match current Nimbus tree.#41 changed
internal/infrastructure/mdparser, which is a build input ofeval-supervisor, so the frozen source hash and static binary hash went stale. This also shows up as failures on unrelated PRs like #42.This regenerates
eval/nimbus/v1/freeze.jsonwith go1.26.4 (the pinned toolchain), reusing the already-audited runtime image IDs from the committed freeze since the pinned verifier image didn't change. The diff is exactly two hashes:staticBinaryInputs:.../internal/infrastructure/mdparserstaticBinaries:eval-supervisorVerified locally:
go run ./eval/cmd/eval nimbus freeze --root eval/nimbus/v1reports a matchgo test ./eval/internal/nimbus/passes🤖 Generated with Claude Code