Skip to content

fix(deps): update all non-major dependencies #52

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
Merged
merged 1 commit into from
Jul 10, 2025
Merged

fix(deps): update all non-major dependencies #52

merged 1 commit into from
Jul 10, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 10, 2025

This PR contains the following updates:

Package Change Age Confidence Type Update
@emotion/core (source) ^10.0.14 -> ^10.3.1 age confidence dependencies minor
@types/node (source) ^22.16.0 -> ^22.16.2 age confidence devDependencies patch
emotion (source) ^10.0.14 -> ^10.0.27 age confidence dependencies patch
pnpm (source) 10.12.4 -> 10.13.1 age confidence packageManager minor
puppeteer (source) ^24.12.0 -> ^24.12.1 age confidence devDependencies patch
react (source) ^16.8.6 -> ^16.14.0 age confidence dependencies minor
react-dom (source) ^16.8.6 -> ^16.14.0 age confidence dependencies minor
rolldown-vite (source) ^7.0.6 -> ^7.0.7 age confidence devDependencies patch
unicode-10.0.0 ^0.7.4 -> ^0.7.5 age confidence dependencies patch
vite (source) ^7.0.3 -> ^7.0.4 age confidence devDependencies patch
vscode ^1.33.0 -> ^1.101.2 age confidence engines minor
webpack ^5.99.9 -> ^5.100.0 age confidence devDependencies minor

Release Notes

emotion-js/emotion (@​emotion/core)

v10.3.1

Compare Source

Patch Changes
  • #​2576 33c01578 Thanks @​Methuselah96! - Export Keyframes type to avoid TypeScript inserting import("@​emotion/serialize").Keyframes references into declaration files emitted based on a source files exporting keyframes result. This avoids issues with strict package managers that don't allow accessing undeclared dependencies.

v10.3.0

Compare Source

Minor Changes

v10.1.1

Compare Source

Patch Changes

  • fe30cbd6 #​2066 Thanks @​Andarist! - Fixed an issue with React giving warning about static children not having unique keys when using the classic jsx factory. This example illustrates the situation in which this has been incorrectly happening:

    <div css={{ color: 'hotpink' }}>
  <div />
  <div />
</div>

v10.1.0

Compare Source

Minor Changes

  • 71514b06 #​1970 Thanks @​FLGMwt! - Support for the new JSX runtimes has been added. They require compatible React versions and shouldn't be manually used.

    To use them you can use the new @jsxImportSource @&#8203;emotion/core pragma instead of the old @jsx jsx or you can use @emotion/babel-preset-css-prop with { runtime: 'automatic' } option to have it handled automatically for you for the whole project.

v10.0.35

Compare Source

Patch Changes
  • 2cf3b16b #​1973 Thanks @​santialbo! - Fixed label extraction from the stack traces in node for components wrapped in React.forwardRef. This has affected only development builds.

v10.0.34

Compare Source

Patch Changes
  • 4979ebb2 #​1966 Thanks @​chnakamura! - Fixed label extraction from the stack traces in Chrome in certain scenarios. This has affected only development builds.

v10.0.28

Compare Source

Patch Changes
  • d0b2a94 #​1714 Thanks @​Andarist! - Fixed label extraction from the stack traces in FireFox and Safari. We have failed to match a label in Emotion wrappers like Theme UI which caused SSR mismatches in mentioned browsers. This has affected only development builds.

v10.0.27

Compare Source

Patch Changes

v10.0.22

Compare Source

Patch Changes

v10.0.21

Compare Source

Patch Changes

v10.0.20

Compare Source

Patch Changes

v10.0.17

Compare Source

v10.0.16

Compare Source

v10.0.15

Compare Source

pnpm/pnpm (pnpm)

v10.13.1

Compare Source

Patch Changes
  • Run user defined pnpmfiles after pnpmfiles of plugins.

v10.13.0

Compare Source

Minor Changes

  • Added the possibility to load multiple pnpmfiles. The pnpmfile setting can now accept a list of pnpmfile locations #​9702.

  • pnpm will now automatically load the pnpmfile.cjs file from any config dependency named @pnpm/plugin-* or pnpm-plugin-* #​9729.

    The order in which config dependencies are initialized should not matter — they are initialized in alphabetical order. If a specific order is needed, the paths to the pnpmfile.cjs files in the config dependencies can be explicitly listed using the pnpmfile setting in pnpm-workspace.yaml.

Patch Changes
  • When patching dependencies installed via pkg.pr.new, treat them as Git tarball URLs #​9694.
  • Prevent conflicts between local projects' config and the global config in dangerouslyAllowAllBuilds, onlyBuiltDependencies, onlyBuiltDependenciesFile, and neverBuiltDependencies #​9628.
  • Sort keys in pnpm-workspace.yaml with deep #​9701.
  • The pnpm rebuild command should not add pkgs included in ignoredBuiltDependencies to ignoredBuilds in node_modules/.modules.yaml #​9338.
  • Replaced shell-quote with shlex for quoting command arguments #​9381.
facebook/react (react)

v16.14.0

Compare Source

React

v16.13.1

Compare Source

React DOM
  • Fix bug in legacy mode Suspense where effect clean-up functions are not fired. This only affects users who use Suspense for data fetching in legacy mode, which is not technically supported. (@​acdlite in #​18238)
  • Revert warning for cross-component updates that happen inside class render lifecycles (componentWillReceiveProps, shouldComponentUpdate, and so on). (@​gaearon in #​18330)

v16.13.0

Compare Source

React
React DOM
Concurrent Mode (Experimental)

v16.12.0

Compare Source

React DOM
React Is

v16.11.0

Compare Source

React DOM
  • Fix mouseenter handlers from firing twice inside nested React containers. @​yuanoook in #​16928
  • Remove unstable_createRoot and unstable_createSyncRoot experimental APIs. (These are available in the Experimental channel as createRoot and createSyncRoot.) (@​acdlite in #​17088)

v16.10.2

Compare Source

React DOM
  • Fix regression in react-native-web by restoring order of arguments in event plugin extractors (@​necolas in #​16978)

v16.10.1

Compare Source

React DOM
  • Fix regression in Next.js apps by allowing Suspense mismatch during hydration to silently proceed (@​sebmarkbage in #​16943)

v16.10.0

Compare Source

React DOM
Scheduler (Experimental)
  • Improve queue performance by switching its internal data structure to a min binary heap. (@​acdlite in #​16245)
  • Use postMessage loop with short intervals instead of attempting to align to frame boundaries with requestAnimationFrame. (@​acdlite in #​16214)
useSubscription
  • Avoid tearing issue when a mutation happens and the previous update is still in progress. (@​bvaughn in #​16623)

v16.9.0

Compare Source

React
  • Add <React.Profiler> API for gathering performance measurements programmatically. (@​bvaughn in #​15172)
  • Remove unstable_ConcurrentMode in favor of unstable_createRoot. (@​acdlite in #​15532)
React DOM
React DOM Server
React Test Utilities and Test Renderer
ESLint Plugin: React Hooks
vitejs/rolldown-vite (rolldown-vite)

v7.0.7

Compare Source

Features
Bug Fixes
  • disable refresh for non-jsx without react import (#​318) (de24b6b)
Code Refactoring
Build System
vitejs/vite (vite)

v7.0.4

Compare Source

Bug Fixes
  • allow resolving bare specifiers to relative paths for entries (#​20379) (324669c)
Build System
microsoft/vscode (vscode)

v1.101.2: May 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.101.1: May 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.101.0: May 2025

Compare Source

Welcome to the May 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

MCP

  • Expand your agent coding flow with support for prompts, resources, and sampling (Show more).
  • Access MCP servers that require authentication (Show more).
  • Debug MCP servers with development mode (Show more).
  • Publish MCP servers from an extension (Show more).

Chat

  • Group and manage related tools by combining them in a tool set (Show more).

Source Control

  • View files in Source Control Graph view (Show more).
  • Assign and track work for GitHub Copilot Coding Agent from within VS Code (Show more).

If you'd like to read these release notes online, go to Updates on code.visualstudio.com.

Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

v1.100.3: April 2025 Recovery 3

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

v1.100.2: April 2025 Recovery 2

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

v1.100.1: April 2025 Recovery 1

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

v1.100.0: April 2025

Compare Source

Welcome to the April 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

  • Chat

    • Custom instructions and reusable prompts (more...).
    • Smarter results with tools for GitHub, extensions, and notebooks (more...).
    • Image and Streamable HTTP support for MCP (more...).

  • Chat performance

    • Faster responses on repeat chat requests (more...).
    • Faster edits in agent mode (more...).

  • Editor experience

    • Improved multi-window support for chat and editors (more...).
    • Staged changes now easier to identify (more...).

For the complete release notes go to Updates on code.visualstudio.com.

Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

v1.99.3: March 2025 Recovery 3

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.99.2: March 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.99.1: March 2025 Recovery 1

Compare Source

The update has a fix for the security vulnerability in this issue.

For the complete release notes go to Updates on code.visualstudio.com.

v1.99.0: March 2025

Compare Source

Welcome to the March 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

  • Agent mode

    • Agent mode is available in VS Code Stable. Enable it by setting chat.agent.enabled:true (more...).
    • Extend agent mode with Model Context Protocol (MCP) server tools (more...).
    • Try the new built-in tools in agent mode for fetching web content, finding symbol references, and deep thinking (more...).

  • Code editing

    • Next Edit Suggestions is now generally available (more...).
    • Benefit from fewer distractions such as diagnostics events while AI edits are applied in the editor (more...).

  • Chat

    • Use your own API keys to access more language models in chat (preview) (more...).
    • Easily switch between ask, edit, and agent mode from the unified chat experience (more...).
    • Experience improved workspace search speed and accuracy with instant remote workspace indexing (more...).

  • Notebook editing

    • Create and edit notebooks as easily as code files with support for edit and agent mode (more...).

For the complete release notes go to Updates on code.visualstudio.com.

Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

v1.98.2: February 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.98.1: February 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.98.0: February 2025

Compare Source

Welcome to the February 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

For the complete release notes go to Updates on code.visualstudio.com.

Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. And for the latest Visual Studio Code news, updates, and content, follow us on Bluesky vscode.dev or Twitter @​code!

v1.97.2: January 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.97.1: January 2025 Recovery 1

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

v1.97.0: January 2025

Compare Source

Welcome to the January 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

For the complete release notes go to Updates on code.visualstudio.com.

Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. And for the latest Visual Studio Code news, updates, and content, follow us on Bluesky vscode.dev or Twitter @​code!

v1.96.4: November 2024 Recovery 4

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.96.3: November 2024 Recovery 3

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.96.2: November 2024 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.96.1: November 2024 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.96.0: November 2024

Compare Source

Welcome to the November 2024 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

For the complete release notes go to Updates on code.visualstudio.com.

Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. And for the latest Visual Studio Code news, updates, and content, follow us on Twitter @​code!

v1.95.3: October 2024 Recovery 3

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.95.2: October 2024 Recovery 2

[Compare Source](https://redirect.github.com/microsoft/vscode/compare/1.95

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), 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.

@chenjiahan chenjiahan merged commit b19eef2 into main Jul 10, 2025
7 checks passed
@chenjiahan chenjiahan deleted the renovate/all-minor-patch branch July 10, 2025 11:07
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.
1 participant
@chenjiahan