chore(interp): long64 php8.5 - #18
Merged
Merged
Conversation
|
Contributor
Author
Class A MetricsCommit Baseline: the last passing master run at PASS - 15 check(s) evaluated, 2 skipped Reading
Not Collected
|
gmitch215
approved these changes
Aug 29, 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.
Fetched from
drupflare/phasmand verified. Nothing here deploys.long648.59674599820n/an/aThis branch is the single proposal line for
long64 php8.5; a newer phasm build force-pushes onto it rather than opening another pull request.The payload carrying these bytes is attached to run 33240079589.
The rollback unit is a Worker version, so ship this on its own.
This branch is red until the bytes are published, and that is expected. It moves
interp.lock.jsononly. Every clean checkout and every CI run restores.interp/from theCDN, which still serves the previous binary, so
interp-pin-agreement.spec.tsreports thetwo files disagreeing. Publishing is the other half and needs R2 credentials this workflow
does not carry:
Commit the rewritten manifest onto this branch and the gate goes green.