Skip to content

build: update all non-major dependencies #30721

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

build: update all non-major dependencies #30721

wants to merge 1 commit into from
+409 −346

Conversation

angular-robot
Copy link
Collaborator

@angular-robot angular-robot commented Jul 16, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
@modelcontextprotocol/sdk (source) dependencies minor 1.15.1 -> 1.16.0
algoliasearch (source) dependencies minor 5.32.0 -> 5.34.0
esbuild optionalDependencies patch 0.25.6 -> 0.25.7
esbuild dependencies patch 0.25.6 -> 0.25.7
esbuild devDependencies patch 0.25.6 -> 0.25.7
esbuild-wasm dependencies patch 0.25.6 -> 0.25.7
esbuild-wasm devDependencies patch 0.25.6 -> 0.25.7
eslint-config-prettier devDependencies patch 10.1.5 -> 10.1.8
google-github-actions/auth action patch v2.1.10 -> v2.1.11
less (source) dependencies minor 4.3.0 -> 4.4.0
less (source) devDependencies minor 4.3.0 -> 4.4.0
picomatch dependencies patch 4.0.2 -> 4.0.3
undici (source) devDependencies minor 7.11.0 -> 7.12.0
vite (source) dependencies patch 7.0.4 -> 7.0.5

Release Notes

modelcontextprotocol/typescript-sdk (@​modelcontextprotocol/sdk)

v1.16.0

Compare Source

What's Changed

New Contributors 🙏

Full Changelog: modelcontextprotocol/typescript-sdk@1.15.1...1.16.0

algolia/algoliasearch-client-javascript (algoliasearch)

v5.34.0

Compare Source

v5.33.0

Compare Source

evanw/esbuild (esbuild)

v0.25.7

Compare Source

  • Parse and print JavaScript imports with an explicit phase (#​4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";
const bar = await import.source("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer * as foo from "<specifier>" or import defer { foo } from "<specifier>".

    This change only adds support for this syntax. These imports cannot currently be bundled by esbuild. To use these new features with esbuild's bundler, the imported paths must be external to the bundle and the output format must be set to esm.

  • Support optionally emitting absolute paths instead of relative paths (#​338, #​2082, #​3023)

    This release introduces the --abs-paths= feature which takes a comma-separated list of situations where esbuild should use absolute paths instead of relative paths. There are currently three supported situations: code (comments and string literals), log (log message text and location info), and metafile (the JSON build metadata).

    Using absolute paths instead of relative paths is not the default behavior because it means that the build results are no longer machine-independent (which means builds are no longer reproducible). Absolute paths can be useful when used with certain terminal emulators that allow you to click on absolute paths in the terminal text and/or when esbuild is being automatically invoked from several different directories within the same script.

  • Fix a TypeScript parsing edge case (#​4241)

    This release fixes an edge case with parsing an arrow function in TypeScript with a return type that's in the middle of a ?: ternary operator. For example:

    x = a ? (b) : c => d;
y = a ? (b) : c => d : e;

    The : token in the value assigned to x pairs with the ? token, so it's not the start of a return type annotation. However, the first : token in the value assigned to y is the start of a return type annotation because after parsing the arrow function body, it turns out there's another : token that can be used to pair with the ? token. This case is notable as it's the first TypeScript edge case that esbuild has needed a backtracking parser to parse. It has been addressed by a quick hack (cloning the whole parser) as it's a rare edge case and esbuild doesn't otherwise need a backtracking parser. Hopefully this is sufficient and doesn't cause any issues.

  • Inline small constant strings when minifying

    Previously esbuild's minifier didn't inline string constants because strings can be arbitrarily long, and this isn't necessarily a size win if the string is used more than once. Starting with this release, esbuild will now inline string constants when the length of the string is three code units or less. For example:

    // Original code
const foo = 'foo'
console.log({ [foo]: true })

// Old output (with --minify --bundle --format=esm)
var o="foo";console.log({[o]:!0});

// New output (with --minify --bundle --format=esm)
console.log({foo:!0});

    Note that esbuild's constant inlining only happens in very restrictive scenarios to avoid issues with TDZ handling. This change doesn't change when esbuild's constant inlining happens. It only expands the scope of it to include certain string literals in addition to numeric and boolean literals.

prettier/eslint-config-prettier (eslint-config-prettier)

v10.1.8

republish latest version

Full Changelog: prettier/eslint-config-prettier@v10.1.5...v10.1.8

google-github-actions/auth (google-github-actions/auth)

v2.1.11

Compare Source

What's Changed

Full Changelog: google-github-actions/auth@v2.1.10...v2.1.11

less/less.js (less)

v4.4.0

Compare Source

micromatch/picomatch (picomatch)

v4.0.3

Compare Source

nodejs/undici (undici)

v7.12.0

Compare Source

What's Changed
New Contributors

Full Changelog: nodejs/undici@v7.11.0...v7.12.0

vitejs/vite (vite)

v7.0.5

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, 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 has been generated by Renovate Bot.

@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project labels Jul 16, 2025
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch 2 times, most recently from a364b95 to 578b84c Compare July 16, 2025 18:06
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch 7 times, most recently from 6131892 to 98766d5 Compare July 18, 2025 21:36
@angular-robot
build: update all non-major dependencies
199b296 
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch from 98766d5 to 199b296 Compare July 18, 2025 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@clydin clydin clydin approved these changes

Assignees
No one assigned
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@angular-robot @clydin