-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): strict regex for package.json and yarn #822
Conversation
✅ Deploy Preview for api-clients-automation canceled.
|
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
.github/workflows/check.yml
Outdated
@@ -54,6 +54,11 @@ jobs: | |||
yarn eslint --ext=json . | |||
echo 'Use yarn fix:json to fix issues' | |||
|
|||
- name: Validate renovate.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The validator takes at least 30 seconds tu run, on each PR, either we cache the renovate file or remove this, wdyt ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not something that should change regularly, we don't have to validate it imo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(alternatively, this could be in a if with a git diff on the renovate but maybe it's overkill)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep I agree, we already some form of validation with the schema anyway
🧭 What and Why
In #532 the regex for
package.mustache
and.yarnrc.yml
are too broad and detect things that don't have versions,this should help renovate to find only real deps.