Skip to content

build: update all non-major dependencies (main) #32034

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
Closed
angular-robot wants to merge 1 commit into from
Closed

build: update all non-major dependencies (main) #32034

angular-robot wants to merge 1 commit into from

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented Dec 5, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@modelcontextprotocol/sdk (source) 1.24.0 -> 1.24.2 age adoption passing confidence
@vitest/coverage-v8 (source) 4.0.14 -> 4.0.15 age adoption passing confidence
esbuild 0.27.0 -> 0.27.1 age adoption passing confidence
esbuild-wasm 0.27.0 -> 0.27.1 age adoption passing confidence
rolldown (source) 1.0.0-beta.52 -> 1.0.0-beta.53 age adoption passing confidence
verdaccio (source) 6.2.3 -> 6.2.4 age adoption passing confidence
vitest (source) 4.0.14 -> 4.0.15 age adoption passing confidence

Release Notes

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

v1.24.2

Compare Source

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/typescript-sdk@1.24.1...1.24.2

v1.24.1

Compare Source

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/typescript-sdk@1.24.0...1.24.1

vitest-dev/vitest (@​vitest/coverage-v8)

v4.0.15

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub
evanw/esbuild (esbuild)

v0.27.1

Compare Source

  • Fix bundler bug with var nested inside if (#​4348)

    This release fixes a bug with the bundler that happens when importing an ES module using require (which causes it to be wrapped) and there's a top-level var inside an if statement without being wrapped in a { ... } block (and a few other conditions). The bundling transform needed to hoist these var declarations outside of the lazy ES module wrapper for correctness. See the issue for details.

  • Fix minifier bug with for inside try inside label (#​4351)

    This fixes an old regression from version v0.21.4. Some code was introduced to move the label inside the try statement to address a problem with transforming labeled for await loops to avoid the await (the transformation involves converting the for await loop into a for loop and wrapping it in a try statement). However, it introduces problems for cross-compiled JVM code that uses all three of these features heavily. This release restricts this transform to only apply to for loops that esbuild itself generates internally as part of the for await transform. Here is an example of some affected code:

    // Original code
d: {
  e: {
    try {
      while (1) { break d }
    } catch { break e; }
  }
}

// Old output (with --minify)
a:try{e:for(;;)break a}catch{break e}

// New output (with --minify)
a:e:try{for(;;)break a}catch{break e}

  • Inline IIFEs containing a single expression (#​4354)

    Previously inlining of IIFEs (immediately-invoked function expressions) only worked if the body contained a single return statement. Now it should also work if the body contains a single expression statement instead:

    // Original code
const foo = () => {
  const cb = () => {
    console.log(x())
  }
  return cb()
}

// Old output (with --minify)
const foo=()=>(()=>{console.log(x())})();

// New output (with --minify)
const foo=()=>{console.log(x())};

  • The minifier now strips empty finally clauses (#​4353)

    This improvement means that finally clauses containing dead code can potentially cause the associated try statement to be removed from the output entirely in minified builds:

    // Original code
function foo(callback) {
  if (DEBUG) stack.push(callback.name);
  try {
    callback();
  } finally {
    if (DEBUG) stack.pop();
  }
}

// Old output (with --minify --define:DEBUG=false)
function foo(a){try{a()}finally{}}

// New output (with --minify --define:DEBUG=false)
function foo(a){a()}

  • Allow tree-shaking of the Symbol constructor

    With this release, calling Symbol is now considered to be side-effect free when the argument is known to be a primitive value. This means esbuild can now tree-shake module-level symbol variables:

    // Original code
const a = Symbol('foo')
const b = Symbol(bar)

// Old output (with --tree-shaking=true)
const a = Symbol("foo");
const b = Symbol(bar);

// New output (with --tree-shaking=true)
const b = Symbol(bar);
rolldown/rolldown (rolldown)

v1.0.0-beta.53

Compare Source

💥 BREAKING CHANGES
🚀 Features
🐛 Bug Fixes
🚜 Refactor
📚 Documentation
⚡ Performance
  • rolldown_plugin_vite_css_post: lazily load cssScopeTo from JS module options (#​7253) by @​shulaoda
  • rolldown_plugin_vite_css_post: avoid unnecessary string clones in resolve_asset_urls_in_css (#​7250) by @​shulaoda
🧪 Testing
⚙️ Miscellaneous Tasks
❤️ New Contributors
verdaccio/verdaccio (verdaccio)

v6.2.4

Compare Source

What's Changed

VERDACCIO_ADDRESS Environment Variable for Docker

You can now set the VERDACCIO_ADDRESS environment variable to control Verdaccio’s network bind address.

  • Choose IPv4 (0.0.0.0), IPv6 ([::]), or a specific interface.
  • Improves compatibility for dual-stack and custom environments.

Example:

docker run -e VERDACCIO_ADDRESS=0.0.0.0 ...
docker run -e VERDACCIO_ADDRESS='[::]' ...

More info at : https://verdaccio.org/docs/env/

Full Changelog: verdaccio/verdaccio@v6.2.3...v6.2.4

Configuration

📅 Schedule: Branch creation - "after 6am and before 10am on Monday, Wednesday, Friday" in timezone Europe/Rome, 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 target: automation This PR is targeted to only merge into the branch defined in Github [bot use only] labels Dec 5, 2025
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this pull request Dec 5, 2025
@alan-agius4
build: update all non-major dependencies
59a5b3d 
See associated pull request for more information.

Closes angular#32034 as a pr takeover
@alan-agius4 alan-agius4 mentioned this pull request Dec 5, 2025
Merged
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this pull request Dec 5, 2025
@alan-agius4
build: update all non-major dependencies
22aca00 
See associated pull request for more information.

Closes angular#32034 as a pr takeover
@angular-robot
build: update all non-major dependencies
af770dc 
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/main-all-non-major-dependencies branch from 5ccb47c to af770dc Compare December 5, 2025 08:42
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this pull request Dec 5, 2025
@alan-agius4
build: update all non-major dependencies
b336b03 
See associated pull request for more information.

Closes angular#32034 as a pr takeover
alan-agius4 added a commit that referenced this pull request Dec 5, 2025
@alan-agius4
build: update all non-major dependencies
7038ea1 
See associated pull request for more information.

Closes #32034 as a pr takeover
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

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only]

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@angular-robot