Repository navigation
devnet-1: pin Spamoor to master-456d075 - #15
Merged
Merged
Conversation
…ormat spamoor#312 switches master to the devnet-2 frame tx format, which devnet-1 rejects. Pin the current master image so devnet-1 keeps sending devnet-1 frame txs after it merges.
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.
spamoor#312 switches master to the bogota-devnet-2 frame tx format (
fees=[max_fee, max_priority_fee_per_gas]), which devnet-1 rejects. devnet-1 runsmaster-latestwithpullPolicy: Always, so the next pod restart after #312 merges would stop all frame traffic.This pins
master-456d075, the imagemaster-latestcurrently points to (same digestsha256:16a2ddbc858e…), so nothing changes on deploy. Merge before spamoor#312. Alternative after #312: back tomaster-latestwith--legacy-frame-feesincustomArgs.