Skip to content

fix(deps): update all non-major dependencies with stable versions (minor) #723

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update all non-major dependencies with stable versions (minor) #723

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 29, 2025 •
edited
Loading

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

This PR contains the following updates:

Package Change Age Confidence Type Update
@evilmartians/lefthook ^1.12.3 -> ^1.13.6 age confidence devDependencies minor
cross-env ^10.0.0 -> ^10.1.0 age confidence devDependencies minor
node (source) 24.6.0 -> 24.9.0 age confidence minor
node (source) 24.6.0 -> 24.9.0 age confidence volta minor
pnpm (source) 10.14.0 -> 10.18.0 age confidence volta minor
sass ^1.90.0 -> ^1.93.2 age confidence devDependencies minor
sass-embedded ^1.90.0 -> ^1.93.2 age confidence devDependencies minor
shiki (source) ^3.8.1 -> ^3.13.0 age confidence dependencies minor
vue-tsc (source) ^3.0.5 -> ^3.1.0 age confidence devDependencies minor

Warning

Deprecated preset: Kong/public-shared-renovate:kong-frontend-config

Your config references a deprecated preset. To prevent disruption, this file now composes the org default building blocks and layers a few tweaks so behavior stays close to the historical frontend configuration.

What’s different from the default

  • Weekday automerge cadence and daily run windows (schedule:automergeWeekdays + schedule:daily + :noUnscheduledUpdates)
  • Automerge enabled for minor and patch updates with required status checks
  • Adds the mend-bot label alongside Renovate’s standard dependency labeling
  • Timezone set to America/New_York
  • Disables specific actions: Kong/kong-api-tests and the-actions-org/workflow-dispatch
  • Extra grouping for GitHub Actions: non-major stable updates grouped under "non-major github actions with stable versions"

Recommended migration

Prefer switching to the default preset and applying only the bits you still need locally. Example configuration to replicate this preset’s behavior on top of the default:

{
  "extends": [
    "Kong/public-shared-renovate",
    "schedule:automergeWeekdays",
    "schedule:daily",
    ":automergeMinor",
    ":automergePatch",
    ":automergeRequireAllStatusChecks",
    ":labels(dependencies,mend-bot)",
    ":noUnscheduledUpdates",
    ":timezone(America/New_York)"
  ],
  "packageRules": [
    {
      "matchPackageNames": ["*"],
      "matchDepTypes": ["action"],
      "matchUpdateTypes": ["minor", "patch"],
      "matchCurrentVersion": "!/^v0/",
      "groupName": "non-major github actions with stable versions"
    }
  ]
}

To disable the same actions locally, add the helpers after the default in your extends list:

[
  "Kong/public-shared-renovate",
  "Kong/public-shared-renovate//helpers/disable-action(Kong/kong-api-tests)",
  "Kong/public-shared-renovate//helpers/disable-action(the-actions-org/workflow-dispatch)"
]

Timeline

This compatibility preset will be removed in January 2026. Please migrate to the default preset with local overrides before then.

Release Notes

evilmartians/lefthook (@​evilmartians/lefthook)

v1.13.6

Compare Source

v1.13.5

Compare Source

v1.13.4

Compare Source

v1.13.3

Compare Source

v1.13.2

Compare Source

v1.13.1

Compare Source

v1.13.0

Compare Source

v1.12.4

Compare Source

kentcdodds/cross-env (cross-env)

v10.1.0

Compare Source

nodejs/node (node)

v24.9.0: 2025-09-25, Version 24.9.0 (Current), @​targos

Compare Source

Notable Changes
  • [9b043a9096] - (SEMVER-MINOR) http: add shouldUpgradeCallback to let servers control HTTP upgrades (Tim Perry) #​59824
  • [a6456ab90a] - (SEMVER-MINOR) sqlite: cleanup ERM support and export Session class (James M Snell) #​58378
  • [5563361d22] - (SEMVER-MINOR) sqlite: add tagged template (0hm☘️) #​58748
  • [04013ee933] - (SEMVER-MINOR) worker: add heap profile API (theanarkh) #​59846
Commits
pnpm/pnpm (pnpm)

v10.18.0

Compare Source

Minor Changes

  • Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

    Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
    Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

    Related PR: #​10025.

Patch Changes
  • Retry filesystem operations on EAGAIN errors #​9959.
  • Outdated command respects minimumReleaseAge configuration #​10030.
  • Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
  • Don't fail with a meaningless error when scriptShell is set to false #​8748.
  • pnpm dlx should not fail when minimumReleaseAge is set #​10037.

v10.17.1

Compare Source

Patch Changes
  • When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #​9974.
  • Fix state.json creation path when executing pnpm patch in a workspace project #​9733.
  • When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #​9987.

v10.17.0

Compare Source

Minor Changes

  • The minimumReleaseAgeExclude setting now supports patterns. For instance:

    minimumReleaseAge: 1440
minimumReleaseAgeExclude:
  - "@​eslint/*"

    Related PR: #​9984.

Patch Changes
  • Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #​9978.
  • When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #​9979.

v10.16.1

Compare Source

Patch Changes
  • The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #​9963.
  • Forcibly disable ANSI color codes when generating patch diff #​9914.

v10.16.0

Compare Source

Minor Changes

  • There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

    The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

    If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:

    minimumReleaseAgeExclude:
  - webpack

    Related issue: #​9921.

  • Added support for finders #​9946.

    In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:

    pnpm why minimist

    prints the chain of dependencies to any installed instance of minimist:

    verdaccio 5.20.1
├─┬ handlebars 4.7.7
│ └── minimist 1.2.8
└─┬ mv 2.1.1
  └─┬ mkdirp 0.5.6
    └── minimist 1.2.8

    What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

    This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

    Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:

    module.exports = {
  finders: {
    react17: (ctx) => {
      return ctx.readManifest().peerDependencies?.react === "^17.0.0";
    },
  },
};

    Now we can use this finder function by running:

    pnpm why --find-by=react17

    pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.

    @&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
└── graphql-tag 2.12.6

    It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:

    module.exports = {
  finders: {
    react17: (ctx) => {
      const manifest = ctx.readManifest();
      if (manifest.peerDependencies?.react === "^17.0.0") {
        return `license: ${manifest.license}`;
      }
      return false;
    },
  },
};

    Every matched package will also print out the license from its package.json:

    @&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
│   license: MIT
└── graphql-tag 2.12.6
    license: MIT
Patch Changes
  • Fix deprecation warning printed when executing pnpm with Node.js 24 #​9529.
  • Throw an error if nodeVersion is not set to an exact semver version #​9934.
  • pnpm publish should be able to publish a .tar.gz file #​9927.
  • Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #​9626.

v10.15.1

Compare Source

Patch Changes
  • Fix .pnp.cjs crash when importing subpath #​9904.
  • When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #​9913.

v10.15.0

Compare Source

Minor Changes
  • Added the cleanupUnusedCatalogs configuration. When set to true, pnpm will remove unused catalog entries during installation #​9793.
  • Automatically load pnpmfiles from config dependencies that are named @*/pnpm-plugin-* #​9780.
  • pnpm config get now prints an INI string for an object value #​9797.
  • pnpm config get now accepts property paths (e.g. pnpm config get catalog.react, pnpm config get .catalog.react, pnpm config get 'packageExtensions["@&#8203;babel/parser"].peerDependencies["@&#8203;babel/types"]'), and pnpm config set now accepts dot-leading or subscripted keys (e.g. pnpm config set .ignoreScripts true).
  • pnpm config get --json now prints a JSON serialization of config value, and pnpm config set --json now parses the input value as JSON.
Patch Changes
  • Semi-breaking. When automatically installing missing peer dependencies, prefer versions that are already present in the direct dependencies of the root workspace package #​9835.
  • When executing the pnpm create command, must verify whether the node version is supported even if a cache already exists #​9775.
  • When making requests for the non-abbreviated packument, add */* to the Accept header to avoid getting a 406 error on AWS CodeArtifact #​9862.
  • The standalone exe version of pnpm works with glibc 2.26 again #​9734.
  • Fix a regression in which pnpm dlx pkg --help doesn't pass --help to pkg #​9823.
sass/dart-sass (sass)

v1.93.2

Compare Source

  • No user-visible changes.
JavaScript API
  • Fix another error in the release process for @sass/types.

v1.93.1

Compare Source

  • No user-visible changes.
JavaScript API
  • Fix an error in the release process for @sass/types.

v1.93.0

Compare Source

  • Fix a crash when a style rule contains a nested @import, and the loaded file
    @uses a user-defined module as well as @includes a top-level mixin which
    emits top-level declarations.
JavaScript API
  • Release a @sass/types package which contains the type annotations used by
    both the sass and sass-embedded package without any additional code or
    dependencies.

v1.92.1

Compare Source

  • Fix a bug where variable definitions from one imported, forwarded module
    would not be passed as implicit configuration to a later imported, forwarded
    module.

v1.92.0

Compare Source

  • Breaking change: Emit declarations, childless at-rules, and comments in
    the order they appear in the source even when they're interleaved with nested
    rules. This obsoletes the mixed-decls deprecation.

  • Breaking change: The function name type() is now fully reserved for the
    plain CSS function. This means that @function definitions with the name
    type will produce errors, while function calls will be parsed as special
    function strings.

  • Configuring private variables using @use ... with, @forward ... with, and
    meta.load-css(..., $with: ...) is now deprecated. Private variables were
    always intended to be fully encapsulated within the module that defines them,
    and this helps enforce that encapsulation.

  • Fix a bug where @extend rules loaded through a mixture of @import and
    @use rules could fail to apply correctly.

Command-Line Interface
  • In --watch mode, delete the source map when the associated source file is
    deleted.

v1.91.0

Compare Source

  • Potentially breaking change: meta.inspect() (as well as other systems
    that use it such as @debug and certain error messages) now emits numbers
    with as high precision as is available instead of rounding to the nearest
    1e⁻¹⁰ as we do when serializing to CSS. This better fits the purpose of
    meta.inspect(), which is to provide full information about the structure of
    a Sass value.

  • Passing a rest argument ($arg...) before a positional or named argument when
    calling a function or mixin is now deprecated. This was always outside the
    specified syntax, but it was historically treated the same as passing the rest
    argument at the end of the argument list whether or not that matched the
    visual order of the arguments.

sass/embedded-host-node (sass-embedded)

v1.93.2

Compare Source

  • No user-visible changes.
JavaScript API
  • Fix another error in the release process for @sass/types.

v1.93.1

Compare Source

  • No user-visible changes.
JavaScript API
  • Fix an error in the release process for @sass/types.

v1.93.0

Compare Source

  • Fix a crash when a style rule contains a nested @import, and the loaded file
    @uses a user-defined module as well as @includes a top-level mixin which
    emits top-level declarations.
JavaScript API
  • Release a @sass/types package which contains the type annotations used by
    both the sass and sass-embedded package without any additional code or
    dependencies.

v1.92.1

Compare Source

  • Fix a bug where variable definitions from one imported, forwarded module
    would not be passed as implicit configuration to a later imported, forwarded
    module.

v1.92.0

Compare Source

  • Breaking change: Emit declarations, childless at-rules, and comments in
    the order they appear in the source even when they're interleaved with nested
    rules. This obsoletes the mixed-decls deprecation.

  • Breaking change: The function name type() is now fully reserved for the
    plain CSS function. This means that @function definitions with the name
    type will produce errors, while function calls will be parsed as special
    function strings.

  • Configuring private variables using @use ... with, @forward ... with, and
    meta.load-css(..., $with: ...) is now deprecated. Private variables were
    always intended to be fully encapsulated within the module that defines them,
    and this helps enforce that encapsulation.

  • Fix a bug where @extend rules loaded through a mixture of @import and
    @use rules could fail to apply correctly.

Command-Line Interface
  • In --watch mode, delete the source map when the associated source file is
    deleted.

v1.91.0

Compare Source

  • Potentially breaking change: meta.inspect() (as well as other systems
    that use it such as @debug and certain error messages) now emits numbers
    with as high precision as is available instead of rounding to the nearest
    1e⁻¹⁰ as we do when serializing to CSS. This better fits the purpose of
    meta.inspect(), which is to provide full information about the structure of
    a Sass value.

  • Passing a rest argument ($arg...) before a positional or named argument when
    calling a function or mixin is now deprecated. This was always outside the
    specified syntax, but it was historically treated the same as passing the rest
    argument at the end of the argument list whether or not that matched the
    visual order of the arguments.

shikijs/shiki (shiki)

v3.13.0

Compare Source

   🚀 Features
    View changes on GitHub

v3.12.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.12.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.12.1

Compare Source

No significant changes

    View changes on GitHub

v3.12.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.11.0

Compare Source

   🚀 Features
    View changes on GitHub

v3.10.0

Compare Source

   🚀 Features
    View changes on GitHub
vuejs/language-tools (vue-tsc)

v3.1.0

Compare Source

Performance
Other Changes

v3.0.8

Compare Source

Features
  • feat(vscode): introduce vue.server.path setting (#​5647)
Bug Fixes
  • fix(language-core): initialize properties of VueVirtualCode in constructor (#​5635) - Thanks to @​KazariEX!
  • fix(vscode): flatten reactivity visualization decorators (#​5642) - Thanks to @​KazariEX!
  • fix(vscode): normalize reactivity visualization ranges
  • fix(vscode): patch typescriptServerPlugin languages without FS hack
  • fix(language-service): do not provide semantic tokens and document highlights for non-file scheme files (#​5653) - Thanks to @​KazariEX!
Performance
  • perf(typescript-plugin): redo single-file language service for reactivity visualization (#​5652)
Other Changes
  • refactor(typescript-plugin): externalize reactivity analysis logic (#​5645) - Thanks to @​KazariEX!

v3.0.7

Compare Source

Bug Fixes
  • fix(vscode): show welcome page only when opening a Vue file
  • fix(language-core): generate slot parameters in the same way as interpolation (#​5618) - Thanks to @​KazariEX!
  • fix(language-core): do not generate variables for builtin directives - Thanks to @​KazariEX!
Other Changes
  • docs(vscode): add descriptions for premium feature configurations (#​5612) - Thanks to @​KazariEX!
  • refactor(typescript-plugin): explicitly request parameters (#​5623)
  • chore(lint): enable @typescript-eslint/no-unnecessary-condition ([#​5630](https://r

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone America/New_York, Automerge - Monday through Friday ( * * * * 1-5 ) in timezone America/New_York.

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) September 29, 2025 07:47
@renovate renovate bot force-pushed the renovate/all-stable branch 2 times, most recently from a7204ad to 1232dbb Compare October 2, 2025 06:37
@renovate
fix(deps): update all non-major dependencies with stable versions
d6ae38b 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/all-stable branch from 1232dbb to d6ae38b Compare October 3, 2025 06:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kongponents-bot kongponents-bot Awaiting requested review from kongponents-bot kongponents-bot is a code owner

@adamdehaven adamdehaven Awaiting requested review from adamdehaven adamdehaven is a code owner

@jillztom jillztom Awaiting requested review from jillztom jillztom is a code owner

@ValeryG ValeryG Awaiting requested review from ValeryG ValeryG is a code owner

@DariaYeremina DariaYeremina Awaiting requested review from DariaYeremina DariaYeremina is a code owner

@vaibhavrajsingh2001 vaibhavrajsingh2001 Awaiting requested review from vaibhavrajsingh2001 vaibhavrajsingh2001 is a code owner

@portikM portikM Awaiting requested review from portikM portikM is a code owner

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
dependencies mend-bot
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants