chore(dependabot): group @swc/core-* updates into one PR #520
Conversation
We aim for @swc/core's manually installed optional dependencies to remain pinned to the same version, but the current dependabot configuration opens two separate PRs: BitGo#513 BitGo#515 This commit configures dependabot to group the @swc/core-* updates into a single PR, to keep both dependencies on the same version at all times.
| groups: | ||
| dependencies: | ||
| patterns: | ||
| - '@swc/core-*' |
There was a problem hiding this comment.
Since the base @swc/core library and the native @swc/core-* optional dependencies appear to be released in sync, should this be @swc/core* instead?
There was a problem hiding this comment.
I believe so! Good catch, thank you
ericcrosson-bitgo
deleted the
chore-dependabot-group-swc/core-updates-into-one-pr
branch
|
🎉 This PR is included in version @api-ts/openapi-generator@2.3.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/typed-express-router@1.1.1 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/express-wrapper@1.0.21 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/superagent-wrapper@1.1.12 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/io-ts-http@2.4.1-beta.1 🎉 The release is available on Your semantic-release bot 📦🚀 |
2 participants
We aim for @swc/core and associated manually-installed optional dependencies to remain pinned to the same version, but the current dependabot configuration opens two separate PRs: #513 #515
This commit configures dependabot to group the @swc/core* updates into a single PR, to keep all @swc/core dependencies on the same version at all times.