Add new zepter duplicate-deps check as part of CI#9809
Merged
bkchr merged 7 commits intoparitytech:masterfrom Sep 26, 2025
Merged
Add new zepter duplicate-deps check as part of CI#9809bkchr merged 7 commits intoparitytech:masterfrom
bkchr merged 7 commits intoparitytech:masterfrom
Conversation
bkchr
approved these changes
Sep 25, 2025
bkchr
added
the
R0-no-crate-publish-required
ggwpez
approved these changes
Sep 25, 2025
Member
ggwpez
left a comment
ggwpez
left a comment
There was a problem hiding this comment.
So we only run this in the CI and not locally?
Okay, i am not sure if it is 100% stable yet so we can keep it like that. In the future i would change it to also run locally then.
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Contributor
Author
@ggwpez what do you mean with locally? |
Merged
via the queue into
paritytech:master
with commit Sep 26, 2025
d5473e6
252 of 257 checks passed
bee344
pushed a commit
that referenced
this pull request
Oct 7, 2025
# Description This PR builds on my previous [PR](#9233) and addresses feedback from Basti’s comment [here](#9283 (comment)). To prevent the same situation from recurring in the future, I’ve introduced a new **lint check** in **Zepter**, which is now also integrated into the CI workflow. The purpose of this check is to automatically detect and block cases where the same dependency is declared both under `[dependencies]` and `[dev-dependencies]`.
alvicsam
pushed a commit
that referenced
this pull request
Oct 17, 2025
# Description This PR builds on my previous [PR](#9233) and addresses feedback from Basti’s comment [here](#9283 (comment)). To prevent the same situation from recurring in the future, I’ve introduced a new **lint check** in **Zepter**, which is now also integrated into the CI workflow. The purpose of this check is to automatically detect and block cases where the same dependency is declared both under `[dependencies]` and `[dev-dependencies]`.
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
3 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.
Description
This PR builds on my previous PR and addresses feedback from Basti’s comment here.
To prevent the same situation from recurring in the future, I’ve introduced a new lint check in Zepter, which is now also integrated into the CI workflow. The purpose of this check is to automatically detect and block cases where the same dependency is declared both under
[dependencies]and[dev-dependencies].