Skip to content

Update all non-major dependencies - #212

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch
Open

Update all non-major dependencies#212
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Jun 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@types/node (source) ^24.13.2 → ^24.13.3 age confidence devDependencies patch
esbuild >=0.28.1 → >=0.28.2 age confidence pnpm-workspace.overrides patch
node (source) 24.16.0 → 24.20.0 age confidence minor
node (source) >=24.15.0 → >=24.20.0 age confidence engines minor
oxc-minify (source) ^0.135.0 → ^0.147.0 age confidence devDependencies minor
pnpm (source) 10.34.4+sha512.8768be55200ae3f2226b6527fcca2687e14bc4e5f12d7721a0f25da3df47915177058648db4177baf348120fa0ba2752d8d8d93f6beaf1fe64ae18da8de961af → 10.34.5 age confidence packageManager patch
vite (source) >=8.0.16 → >=8.2.2 age confidence pnpm-workspace.overrides minor
vitepress (source) 2.0.0-alpha.17 → 2.0.0-alpha.19 age confidence devDependencies patch
vitepress-plugin-tabs (source) ^0.9.0 → ^0.9.1 age confidence devDependencies patch
vue (source) ^3.5.39 → ^3.5.42 age confidence devDependencies patch

Release Notes

evanw/esbuild (esbuild)

v0.28.2

Compare Source

  • Fix tree shaking bug due to TypeScript import alias (#​4507)

    This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

    import Base from './dep.js';
import Alias = Base.SomeType;

  • Fix CSS minification bug involving & (#​4497)

    This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

    /* Original code */
.a .b {
  & .b:not(& .c) {
    color: red;
  }
}

/* Old output (with --minify) */
.a .b{.b:not(& .c){color:red}}

/* New output (with --minify) */
.a .b{& .b:not(& .c){color:red}}

    This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

  • Avoid overwriting input files without --allow-overwrite (#​4484)

    For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

    This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

  • Fix incorrect code generated when using top-level await (#​4498)

    Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

  • Fix a minification bug with lowered logical assignment operators (#​4508)

    This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

    // Original code
function foo() {
  let x
  bar(x ||= {})
}

// Old output (with --minify-syntax --target=es6)
function foo() {
  bar(void 0 || (x = {}));
}

// New output (with --minify-syntax --target=es6)
function foo() {
  let x;
  bar(x || (x = {}));
}

  • Fix a potential deadlock when the JavaScript API is used incorrectly (#​4503, #​4506)

    The JavaScript API runs the native esbuild executable as a long-lived child process and communicates with it over stdin/stdout/stderr. Each API request is asynchronous and the executable stays open as long as it has work to do, which is as long as either stdin is still open (meaning there may be more API requests) or there are currently requests being processed.

    Previously esbuild's tracking of outstanding API requests missed decrementing a reference count in an edge case where esbuild's JavaScript API was used incorrectly and the API request returned an error. This could in some cases cause esbuild's native executable to exit with an error message about a deadlock. This release fixes the reference counting bug.

    This fix was submitted by @​ZuBB.

  • Handle target collisions (#​4509)

    It's possible to specify the same target engine multiple times, such as with --target=chrome1,chrome99. This edge case wasn't anticipated and previously took the last version for the duplicated target engine instead of the minimum version (so chrome99 in this case instead of chrome1). With this release, esbuild will now pick the minimum version between all duplicated target engines.

  • Force .mp3 files to use the audio/mpeg MIME type (#​4485)

    MIME type detection for esbuild's data URLs uses Go's built-in MIME type detection, which is based on the MIME sniffing standard. This works correctly for MP3 files that start with the byte sequence ID3, which is commonly the case. However, it's possible to construct valid MP3 files that do not start with ID3, and that perhaps Go's built-in MIME type detection doesn't implement the "Signature for MP3 without ID3" part of the algorithm. This results in some .mp3 files incorrectly using the application/octet-stream MIME type instead of audio/mpeg. With this release, esbuild will now always use the audio/mpeg MIME type for files ending in .mp3.

  • Add a new TypeScript syntax warning

    TypeScript 7 turned some previously-valid TypeScript syntax into a syntax error because it was confusing. TypeScript 6 accepts 1 + 2 as number * 3 as valid syntax but confusingly converts it to (1 + 2) * 3 instead of the more intuitive conversion to 1 + (2 * 3). This syntax is now an error in TypeScript 7+. With this release, esbuild will now warn about the use of this syntax:

    ▲ [WARNING] Operator "*" should not directly follow a TypeScript type cast after the "+" operator [confusing-typescript-cast]

    example.ts:1:28:
      1 │ console.log(1 + 2 as number * 3)
        ╵                             ^

  This is a syntax error in newer versions of TypeScript because the type cast has unintuitive
  precedence in this case. Surround the inner expression in parentheses to silence this warning:

    example.ts:1:12:
      1 │ console.log(1 + 2 as number * 3)
        │             ~~~~~~~~~~~~~~~
        ╵             (             )

    See microsoft/TypeScript#63527 for more information.

  • Add support for formatting errors for Visual Studio (#​4460)

    Visual Studio has a specific style that it expects log messages to be in for them to show up in the UI when esbuild is run as a custom build step. The current log style that esbuild uses doesn't conform to this specific style.

    With this release, esbuild has a new log style for Visual Studio (and other tools in the MSBuild ecosystem) that can be enabled with --log-style=visualstudio. Here is an example log message in this style:

    $ esbuild example.ts --log-style=visualstudio
/Users/evan/dev/esbuild/example.ts(1,29): warning ES0010: Operator "*" should not directly follow a TypeScript type cast after the "+" operator

    This log style is also available via the JS and Go APIs, and can now be used with the existing formatMessages API.

  • Fix a bug with CSS gamut mapping (#​4488)

    Due to a typo, the fallback colors generated for CSS colors outside of the sRGB gamut weren't correct. This release fixes the generated colors to use the intended algorithm.

    This fix was submitted by @​chatman-media.

nodejs/node (node)

v24.20.0: 2026-08-26, Version 24.20.0 'Krypton' (LTS), @​aduh95

Compare Source

Notable Changes
Commits

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

@netlify

netlify Bot commented Jun 12, 2026 •
edited
Loading

Copy link
Copy Markdown

❌ Deploy Preview for sklauncher-docs failed.

Name Link
🔨 Latest commit 387d116
🔍 Latest deploy log https://app.netlify.com/projects/sklauncher-docs/deploys/6a8feee93b4e5f000800d845

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 6130673 to a6eb055 Compare June 15, 2026 13:07
@renovate renovate Bot changed the title Update all non-major dependencies to v10.34.3 Update all non-major dependencies Jun 15, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from a6eb055 to e2cf6cf Compare June 17, 2026 16:14
@socket-security

socket-security Bot commented Jun 17, 2026 •
edited
Loading

Copy link
Copy Markdown

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from f622e13 to 94c5422 Compare June 24, 2026 01:46
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 3e54f64 to 6dbdbd5 Compare July 2, 2026 05:26
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from f253402 to b50460f Compare July 12, 2026 11:12
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from b5dbd13 to 709c961 Compare July 21, 2026 01:14
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from fb79d95 to e0b148f Compare July 27, 2026 17:55
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 02d4f8f to d12a8b8 Compare August 5, 2026 11:15
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 60255aa to 7ff8448 Compare August 11, 2026 23:05
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 59d5cf3 to 3b228b0 Compare August 20, 2026 06:35
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 3aa57f9 to a18e007 Compare August 26, 2026 16:46
@renovate

renovate Bot commented Aug 26, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package.json
Command failed: corepack use pnpm@10.34.5
File name: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
 ERR_PNPM_NO_MATURE_MATCHING_VERSION  Version 3.5.42 (released 2 hours ago) of vue does not meet the minimumReleaseAge constraint

This error happened while installing a direct dependency of /tmp/renovate/repos/github/sklauncher/docs

The latest release of vue is "3.5.42". Published at 8/27/2026 5:52:49 AM

Other releases are:
  * csp: 1.0.28-csp published at 9/27/2016
  * legacy: 2.7.16 published at 12/24/2023
  * v2-latest: 2.7.16 published at 12/24/2023
  * alpha: 3.6.0-alpha.7 published at 12/12/2025
  * beta: 3.6.0-beta.17 published at 6/24/2026
  * rc: 3.6.0-rc.5 published at 8/21/2026

If you need the full list of all 589 published versions run "pnpm view vue versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from a18e007 to 387d116 Compare August 27, 2026 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants