Pin the active Bifrost candidate to v0.10.5 - #163
Merged
Conversation
v0.10.1 predates the PHP declaration-range fix. Confirmed against the public mirror: php_declaration_name_range, the symbol BrokkAi/bifrost-dev#2416 introduced, is absent from v0.10.4 and present from v0.10.5, so the newest tag at the time would still have left php-property-access and php-parity-static-property-access reporting wrong_target. v0.10.5 is d775e3b4, a projection commit on top of 79ea68cf, which is what the release-readiness run built. It carries both that fix and the summary-spelling round-trip work. The revision is pinned in five places and they have to move together. reference-image.sh refuses to build when the candidate registry and the reference-environment manifest disagree, and the image is addressed by the analyzer identity, so the manifest revision is part of the image's address rather than a description of it. The reproduction contract and the freeze-shard test both assert the exact pair, and the historical v1 page names the active candidate to tell readers its own tables are older evidence -- a live claim that goes stale if it does not follow. Deliberately unchanged: the v0.10.2 pin the contract asserts for candidates-v0.3.0.json. That registry belongs to a frozen release and must keep naming the Bifrost that produced it. This does not re-measure anything. The expected-failure set for the legacy freeze was taken under v0.10.1 and 31 commits have landed since; #160 covers re-baselining it, and #161 covers the overlap between this repository's sigil handling and Bifrost's own leading-dollar fix. Co-Authored-By: Claude Opus 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Unblocks the re-pin prerequisite on #155.
Why v0.10.5 and not v0.10.4
php_declaration_name_range— the symbol BrokkAi/bifrost-dev#2416 introduced —is absent from
v0.10.4(e6d20728, 19 Aug 12:35) and present fromv0.10.5. Pinning the newest tag as of yesterday would have shipped a freezewith the
wrong_targethalf of the PHP cases still broken.v0.10.5isd775e3b4, a projection commit whose parent is79ea68cf— thecommit the release-readiness run
built. Verified it carries both the declaration-range fix and the
summary-spelling round-trip work.
Five pin sites, one identity
adapters/candidates.jsoncontainers/reference/v1/manifest.jsonreference-image.sh:98refuses to build when these disagree; the image is addressed by the analyzer identity, so this is part of the addressscripts/validate-reproduction-contract.sh:73tests/test_freeze_shards.py:60docs/src/content/docs/results/evaluation-real-project-v1.md:16Deliberately unchanged: the
v0.10.2/d1a7c0ccpin the contract assertsfor
candidates-v0.3.0.json. That registry belongs to a frozen release andmust keep naming the Bifrost that produced it.
What this does not do
It does not re-measure anything.
511adaa→d775e3b4is 31 commits and 300files; the expected-failure set in #155 was taken under v0.10.1 and should not
be used to judge a freeze run until it is re-measured (#160). The interaction
between this repository's PHP sigil handling and Bifrost's own leading-dollar
fix is #161.
Testing
cargo test242 passed / 0 failed;test_freeze_shards.py18 passed;validate-reproduction-contract.shexits 0.Note the reference image will rebuild, since its address derives from the
analyzer revision.
🤖 Generated with Claude Code