feat(javascript): use separateMultipleMinor for typescript

since they release breaking changes in minor versions renovatebot/renovate#24538
bettermarks · Mar 25, 2024 · 1fe40a4 · 1fe40a4
1 parent 8b7a448
commit 1fe40a4
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/README.md b/README.md
@@ -184,7 +184,8 @@ and it configures the following:
 - Disable updates for major node versions and prevent pinning to a specific node version 
 - Keep semver ranges in the [`resolutions` field used by yarn](https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/).
 - Update packages from the `@bettermarks/` scope or that start with `bm-` with higher priority(5) than other dependencies and disable `npm:unpublishSafe`.
-- Update the `typescript` dependency with higher priority(2) than other dependencies and disable `npm:unpublishSafe`. Create separate PRs for patch and minor version upgrades, since they introduce breaking changes in minor versions.
+- Update the `typescript` dependency with higher priority(2) than other dependencies and disable `npm:unpublishSafe`. 
+  Create separate PRs for patch and minor and multiple minor version upgrades, since they introduce breaking changes in minor versions.
 - Keep the major version of `@types/jest` in sync with the major version of `jest`.
 - Update packages from the `@types/*` scope with lower priority(-5) than other dependencies and disable `npm:unpublishSafe`.
 

diff --git a/javascript.json b/javascript.json
@@ -36,6 +36,7 @@
     {
       "matchPackageNames": ["typescript"],
       "separateMinorPatch": true,
+      "separateMultipleMinor": true,
       "prPriority": 2
     },
     {