Skip to content

Commit

Permalink
fix zepter
Browse files Browse the repository at this point in the history
  • Loading branch information
klkvr committed Jan 30, 2025
1 parent fd71876 commit 7260e65
Showing 1 changed file with 4 additions and 7 deletions.
11 changes: 4 additions & 7 deletions .config/zepter.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -12,15 +12,13 @@ workflows:
# Check that `A` activates the features of `B`.
"propagate-feature",
# These are the features to check:
"--features=std,serde,arbitrary",
"--features=std",
# Do not try to add a new section into `[features]` of `A` only because `B` expose that feature. There are edge-cases where this is still needed, but we can add them manually.
"--left-side-feature-missing=ignore",
# Ignore the case that `A` it outside of the workspace. Otherwise it will report errors in external dependencies that we have no influence on.

"--left-side-outside-workspace=ignore",
# Auxilary flags:
"--offline",
"--locked",
# limit to the workspace
"--workspace",
"--show-path",
"--quiet",
]
Expand All @@ -31,11 +29,10 @@ workflows:
# Will be displayed when any workflow fails:
help:
text: |
Reth uses the Zepter CLI to detect abnormalities in Cargo features, e.g. missing propagation.
Alloy uses the Zepter CLI to detect abnormalities in Cargo features, e.g. missing propagation.
It looks like one more checks failed; please check the console output.
You can try to automatically address them by installing zepter (`cargo install zepter --locked`) and simply running `zepter` in the workspace root.
links:
- "https://github.com/paradigmxyz/reth/pull/11888"
- "https://github.com/ggwpez/zepter"

0 comments on commit 7260e65

Please sign in to comment.