-
Notifications
You must be signed in to change notification settings - Fork 273
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
ci: add dependabot docker and npm ecosystems #3885
Conversation
This means more dependabot PRs, and hopefully less manual work keeping Dockerfiles up to date. In some cases careful testing will be required before merging Docker PRs but at least we have a to-do list in the form of dependabot PRs. With the npm package ecosystem, dependabot will also start suggesting more NPM updates, and not just the security updates (that's why I limited the number of them until 0.13 has landed).
.github/dependabot.yml
Outdated
# Automatically update NPM packages | ||
- package-ecosystem: "npm" | ||
directory: "/" | ||
open-pull-requests-limit: 3 # for now, once 0.13 landed we can increase this |
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.
I'm slightly hesitant on adding the npm updates right now, in part because of the earlier work on #3838 and discovering the need to configure our typescript project and its build process to support consuming ECMAScript Modules #3841. Currently, we are blocked by this on updating a lot of dependencies, we can't use "pure ESM build" dependencies.
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.
OK, I have commented out the npm ecosystem for now and added a comment that mentions the #3841 ESM packaging issue
We do not use dependabot with npm yet because our build process is currently incompatible with "pure ESM build" dependencies. See also #3841
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.
thanks! 🚀
This means more dependabot PRs, and hopefully less manual work keeping Dockerfiles up to date. In some cases careful testing will be required before merging Docker PRs but at least we have a to-do list in the form of dependabot PRs. We do not use dependabot with npm yet because our build process is currently incompatible with "pure ESM build" dependencies. See also #3841
This means more dependabot PRs, and hopefully less manual work keeping Dockerfiles up to date. In some cases careful testing will be required before merging Docker PRs but at least we have a to-do list in the form of dependabot PRs. We do not use dependabot with npm yet because our build process is currently incompatible with "pure ESM build" dependencies. See also #3841
What this PR does / why we need it:
This means more dependabot PRs, and hopefully less manual work keeping Dockerfiles up to date.
In some cases careful testing will be required before merging Docker PRs but at least we have a to-do list in the form of dependabot PRs.
With the npm package ecosystem, dependabot will also start suggesting more NPM updates, and not just the security updates (that's why I limited the number of them until 0.13 has landed).
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: