Repository navigation
seals: CI seals for seal_check and seal_verdict (Refs #13882) - #13889
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
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.
Commits the CI-generated seals for
specs/verified/seal_check.t27and its importerspecs/t27mcp/seal_verdict.t27. #13885 changedseal_check.t27without its seal, sospec-guardswent red on that PR and the stale count rose by one on master. This PR fixes that regression.Both files are copied byte for byte from the
resealed-sealsartifact. Nothing was edited or saved locally.Auto-merge is enabled only after this PR's
spec-guardsshows a stale count at or below master's.Refs #13882 (the #13885 regression)
🤖 Generated with Claude Code