chore(repo): Configure Dependabot - #3051
Conversation
🦋 Changeset detectedLatest commit: 4be75e5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| update-types: | ||
| - "major" | ||
| - "minor" | ||
| - "patch" |
There was a problem hiding this comment.
I feel like we only wanna apply security patches to core 1, yeah?
| # This configuration will: | ||
| # - Check for updates weekly on Wednesday at 12:00 UTC | ||
| # - Create one pull request at a time | ||
| # - Commit changes with the prefix `chore(repo)` and include the scope |
There was a problem hiding this comment.
I'm confused about this one - why is it run on a different day and whats the difference from the other ones?
There was a problem hiding this comment.
To offset any required changes, but can standardize. This will be way less frequent than the other two.
There was a problem hiding this comment.
Still not sure I understand what this means
There was a problem hiding this comment.
The difference is the package-ecosystem key. So the first one will update the package.json entries, the second one will update the GitHub actions.
LekoArts
left a comment
There was a problem hiding this comment.
See convo in Slack, I'm not sure if Dependabot is the right tool for our use cases
|
Closing this one as it seems we'll be using renovate :) feel free to reopen if this is not the case! |
Description
Configures Dependabot. See code comments for applied settings.
SDK-1557
Checklist
npm testruns as expected.npm run buildruns as expected.Type of change