Skip to content

Commit

Permalink
default: Try to fix peer dependency upgrades
Browse files Browse the repository at this point in the history
These should generally be semantic commits as they allow consumers to
install later peer dependencies without warnings. I'm not sure why we/I
thought to group these beforehand.

I'm keeping the schedule aligned with dev dependencies as it's common to
have a package specified under `devDependencies` and `peerDependencies`.
Ideally these would even be grouped together but that's a challenge for
another day.
  • Loading branch information
72636c committed Feb 29, 2024
1 parent 15b3aef commit d9884e6
Showing 1 changed file with 1 addition and 10 deletions.
11 changes: 1 addition & 10 deletions default.json
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@
"semanticCommitType": "fix"
},
{
"matchDepTypes": ["dependencies"],
"matchDepTypes": ["dependencies", "peerDependencies"],
"matchManagers": ["npm"],

"semanticCommitType": "fix"
Expand Down Expand Up @@ -113,19 +113,10 @@
"schedule": "after 3:00 am and before 6:00 am every 2 weeks on Tuesday"
},
{
"excludePackageNames": ["braid-design-system", "sku", "skuba"],
"excludePackagePatterns": [
"^@?seek",
"seek$",
"^@types/",
"^@vanilla-extract/"
],
"matchDepTypes": ["peerDependencies"],
"matchManagers": ["npm"],
"matchUpdateTypes": ["major", "minor", "patch"],

"commitMessageExtra": "",
"groupName": "npm peer dependencies",
"schedule": "after 3:00 am and before 6:00 am every 2 weeks on Tuesday"
},
{
Expand Down

0 comments on commit d9884e6

Please sign in to comment.