fix: update tempo dependency pins#15156
Merged
Merged
Conversation
mattsse
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy,
mablr and
stevencartavia
as code owners
mattsse
force-pushed
the
mattsse/update-tempo-mpp-pins
branch
from
33e4424 to
9efcb16
Compare
mattsse
force-pushed
the
mattsse/update-tempo-mpp-pins
branch
from
9efcb16 to
6358287
Compare
figtracer
approved these changes
Jun 12, 2026
0xrusowsky
approved these changes
Jun 12, 2026
stevencartavia
approved these changes
Jun 12, 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
4 participants
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.
Updates Foundry's Tempo dependency pins to the current Tempo release state from tempoxyz/tempo#5497 and points
mppat the merged dependency fix from tempoxyz/mpp-rs#295.This keeps Foundry,
mpp, and the[patch.crates-io]Tempo crates resolving from one compatible Tempo source. The CI failure came frommppretaining exact=1.8.0Tempo crate requirements while the Tempo workspace moved to1.8.1, which allowed incompatibletempo_primitivestypes into the same build graph.Impact is limited to the Tempo dependency graph used by the Forge build without default features.