chore: Do not force std with serde feature
#178
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
github-merge-queue bot
pushed a commit
to op-rs/kona
that referenced
this pull request
Aug 19, 2025
## Overview Updates the `zepter` configuration to allow `alloy-hardforks` + `alloy-op-hardforks`' `serde` feature to propagate, since they've now fixed the "serde implies `std`" issue. _note_: The last exception is `miniz_oxide`, which now has the fix merged, but not released: Frommi/miniz_oxide#178
matrix-rider609op
added a commit
to matrix-rider609op/kona
that referenced
this pull request
Sep 29, 2025
## Overview Updates the `zepter` configuration to allow `alloy-hardforks` + `alloy-op-hardforks`' `serde` feature to propagate, since they've now fixed the "serde implies `std`" issue. _note_: The last exception is `miniz_oxide`, which now has the fix merged, but not released: Frommi/miniz_oxide#178
aPTRDgvm5ui3dkEtFYWc
added a commit
to aPTRDgvm5ui3dkEtFYWc/kona
that referenced
this pull request
Oct 2, 2025
## Overview Updates the `zepter` configuration to allow `alloy-hardforks` + `alloy-op-hardforks`' `serde` feature to propagate, since they've now fixed the "serde implies `std`" issue. _note_: The last exception is `miniz_oxide`, which now has the fix merged, but not released: Frommi/miniz_oxide#178
theochap
pushed a commit
to ethereum-optimism/optimism
that referenced
this pull request
Dec 10, 2025
## Overview Updates the `zepter` configuration to allow `alloy-hardforks` + `alloy-op-hardforks`' `serde` feature to propagate, since they've now fixed the "serde implies `std`" issue. _note_: The last exception is `miniz_oxide`, which now has the fix merged, but not released: Frommi/miniz_oxide#178
theochap
pushed a commit
to ethereum-optimism/optimism
that referenced
this pull request
Jan 14, 2026
## Overview Updates the `zepter` configuration to allow `alloy-hardforks` + `alloy-op-hardforks`' `serde` feature to propagate, since they've now fixed the "serde implies `std`" issue. _note_: The last exception is `miniz_oxide`, which now has the fix merged, but not released: Frommi/miniz_oxide#178
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Overview
Removes the implication that enabling the
serdefeature enablesstd.