fix: token-storage-detection image build (prebuilt anvil)#216
Merged
Conversation
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.
The token-storage-detection image build has failed on every release since v1.4.13 (v1.4.16 included). Root cause: the Dockerfile compiles anvil from an unpinned
foundrymain clone inside a pinnedrust:1.92image - the moment foundry's minimum supported rustc passed 1.92, the build died withrustc 1.92.0 is not supported by the following packages.Because the deployment runs
token-storage-detection:latest, prod has been quietly stuck on a stale image - which currently blocks the Robinhood (and MegaETH env-var) slot-detection rollout: theRobinhoodChain enum from #215 never reaches the cluster.Fix: install the pinned prebuilt anvil release binary (
v1.7.1, verified the asset exists and containsanvil) instead of compiling from source. Also shaves ~10 minutes off the image build and addsanvil --versionas a build-time sanity check.After merge: dispatch the release workflow or rebuild the image so
:latestpicks up the enum changes, then restart the token-storage-detection deployment (the prd refresh workflow does this).