Skip to content

chore: Update picomatch and rollup-plugin-typescript2#9892

Draft
hsubox76 wants to merge 3 commits intomainfrom
ch-picomatch-update
Draft

chore: Update picomatch and rollup-plugin-typescript2#9892
hsubox76 wants to merge 3 commits intomainfrom
ch-picomatch-update

Conversation

@hsubox76
Copy link
Copy Markdown
Contributor

Update picomatch for security reasons as per PR #9760

Updating picomatch to 2.3.2 breaks unless rollup-plugin-typescript2 is also updated, so this PR includes that update.

dependabot Bot and others added 3 commits April 23, 2026 18:59
Bumps [picomatch](https://github.com/micromatch/picomatch) from 2.3.1 to 2.3.2.
- [Release notes](https://github.com/micromatch/picomatch/releases)
- [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md)
- [Commits](micromatch/picomatch@2.3.1...2.3.2)

---
updated-dependencies:
- dependency-name: picomatch
  dependency-version: 2.3.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 24, 2026

⚠️ No Changeset found

Latest commit: 3e9ea84

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the version of rollup-plugin-typescript2 to 0.37.0 across multiple packages and includes updates to the yarn.lock file. A critical issue was identified in the yarn.lock changes where the dependencies for sha.js were accidentally removed during entry deduplication, which could lead to installation or runtime errors. It is recommended to regenerate the lockfile to restore these necessary dependencies.

Comment thread yarn.lock
Comment on lines +14939 to 14942
sha.js@^2.4.0, sha.js@^2.4.12, sha.js@^2.4.8:
version "2.4.12"
resolved "https://registry.npmjs.org/sha.js/-/sha.js-2.4.12.tgz#eb8b568bf383dfd1867a32c3f2b74eb52bdbf23f"
integrity sha512-8LzC5+bvI45BjpfXU8V5fdU2mfeKiQe1D1gIMn7XUlF3OTUrpdJpPPH4EMAnF0DsHHdSZqCdSss5qCmJKuiO3w==
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The dependencies section for sha.js has been removed during the deduplication of entries in the lockfile. sha.js version 2.4.12 requires its dependencies (inherits, safe-buffer, and to-buffer) to be correctly defined to ensure they are installed. Removing them will likely cause installation failures or runtime errors. It is recommended to regenerate the lockfile using yarn install to ensure all transitive dependencies are correctly captured.

sha.js@^2.4.0, sha.js@^2.4.12, sha.js@^2.4.8:
  version "2.4.12"
  resolved "https://registry.npmjs.org/sha.js/-/sha.js-2.4.12.tgz#eb8b568bf383dfd1867a32c3f2b74eb52bdbf23f"
  integrity sha512-8LzC5+bvI45BjpfXU8V5fdU2mfeKiQe1D1gIMn7XUlF3OTUrpdJpPPH4EMAnF0DsHHdSZqCdSss5qCmJKuiO3w==
  dependencies:
    inherits "^2.0.4"
    safe-buffer "^5.2.1"
    to-buffer "^1.2.0"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant