chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #69 · unplugin/unplugin-isolated-decl

renovate · 2025-05-12T03:23:27Z

This PR contains the following updates:

Package	Change	Age	Confidence
@oxc-project/types (source)	`^0.127.0` → `^0.138.0`
@typescript/native-preview (source)	`7.0.0-dev.20260422.1` → `7.0.0-dev.20260630.1`
pnpm (source)	`10.33.1` → `10.34.4`
tsdown (source)	`^0.21.9` → `^0.22.0`

Release Notes

microsoft/typescript-go (@typescript/native-preview)

pnpm/pnpm (pnpm)

`v10.34.4`

Compare Source

`v10.34.3`

Compare Source

`v10.34.2`

Compare Source

`v10.34.1`: pnpm 10.34.1

Compare Source

Patch Changes

Reject pnpm-lock.yaml entries whose remote tarball resolution: block is missing the integrity field. Previously the worker that extracts a downloaded tarball skipped hash verification when no integrity was supplied and minted a fresh one from the unverified bytes, so an attacker who could both alter the lockfile (e.g. via a pull request that strips integrity:) and serve modified content at the referenced tarball URL could install a tampered package without any error — including under --frozen-lockfile. pnpm now fails closed at lockfile-read time with ERR_PNPM_MISSING_TARBALL_INTEGRITY. Git-hosted tarballs (gitHosted: true or a URL on codeload.github.com / bitbucket.org / gitlab.com) and file: tarballs are exempt — the commit SHA in a git-host URL and the user-controlled local path already anchor the bytes.

Platinum Sponsors

Gold Sponsors

`v10.34.0`: pnpm 10.34

Compare Source

Minor Changes

Treat tarball-integrity mismatches against the lockfile as a hard failure by default. Previously, pnpm install (non-frozen) would log ERR_PNPM_TARBALL_INTEGRITY, silently re-resolve from the registry, and overwrite the locked integrity — which meant a compromised registry, proxy, or republished version could substitute attacker-controlled content on a clean machine even though the project shipped a committed lockfile.

pnpm install now exits with ERR_PNPM_TARBALL_INTEGRITY and a hint pointing at the new opt-in flag.

The only opt-in is pnpm install --update-checksums — narrowly scoped to refreshing the locked integrity values from what the registry currently serves. Mirrors yarn's flag of the same name. A warning still prints when the bypass takes effect so the operation is auditable.

--force and pnpm update deliberately do not bypass the integrity check. They are routine refresh operations; silently overwriting a locked integrity in those flows would erase the protection a committed lockfile is supposed to provide. --frozen-lockfile behavior is unchanged. --fix-lockfile keeps its documented purpose (filling in missing lockfile entries) and is also not a bypass.

Patch Changes

Pin unscoped per-registry settings (_authToken, _auth, username/_password, tokenHelper, inline cert/key) to the registry declared in the same config source at load time, so a later layer overriding registry= (workspace .npmrc, pnpm-workspace.yaml, CLI --registry) cannot redirect a credential or client certificate authored for a different host. A deprecation warning is emitted whenever an unscoped per-registry setting is encountered, naming the source and the URL it was pinned to. Reported by JUNYI LIU.
Fixed minimumReleaseAge handling when cached metadata is abbreviated. The npm registry returns abbreviated package metadata (without the per-version time field) by default, which made the maturity check throw ERR_PNPM_MISSING_TIME whenever cached abbreviated metadata was reused. pnpm now upgrades cached abbreviated metadata to the full document via a follow-up fetch when minimumReleaseAge is active, persists the upgrade to the on-disk cache so subsequent installs skip the extra fetch, and lets ERR_PNPM_MISSING_TIME from the cache fast-path fall through to the network fetch even under strict mode.
Reject git resolutions whose commit field is not a 40-character hexadecimal SHA before invoking git. A malicious lockfile could otherwise smuggle a value such as --upload-pack=<command> through git fetch / git checkout, which on SSH or local-file transports executes the supplied command.
Reject patch files whose diff --git headers reference paths outside the patched package directory. Previously a malicious .patch file added via a pull request could write, delete, or rename arbitrary files reachable by the user running pnpm install.
Fixed --prefix=<dir> not being honored when locating the workspace root. The --prefix → dir rename was applied after workspace detection, so workspace settings declared in <dir>/pnpm-workspace.yaml were not loaded when pnpm was invoked from outside <dir> #11535.
Reject dependency aliases that contain path-traversal segments (such as @x/../../../../../.git/hooks) when reading them from a package manifest or symlinking them into node_modules. A malicious registry package could otherwise use a transitive dependency key to make pnpm install create symlinks at attacker-chosen paths outside the intended node_modules directory.

Platinum Sponsors

Gold Sponsors

`v10.33.4`: pnpm 10.33.4

Compare Source

Patch Changes

Pin the integrity of git-hosted tarballs (codeload.github.com, gitlab.com, bitbucket.org) in the lockfile so that subsequent installs detect a tampered or substituted tarball and refuse to install it. Previously the lockfile only stored the tarball URL for git dependencies, so a compromised git host or a man-in-the-middle could serve arbitrary code on later installs without lockfile changes.

A new gitHosted: true field is recorded on git-hosted tarball resolutions in the lockfile, letting every reader/writer route them by a single typed check instead of pattern-matching the tarball URL in each call site. Lockfiles written by older pnpm versions are enriched on load (URL fallback) so the field can be relied on uniformly across the codebase.
Fix a regression where pnpm --recursive --filter '!<pkg>' run/exec/test/add would include the workspace root in the matched projects. The workspace root is now correctly excluded by default when only negative --filter arguments are provided, matching the documented behavior. To include the root, pass --include-workspace-root #11341.

Platinum Sponsors

Gold Sponsors

`v10.33.3`

Compare Source

`v10.33.2`

Compare Source

rolldown/tsdown (tsdown)

`v0.22.3`

Compare Source

🚨 Breaking Changes

Drop node 24.0 - 24.10 support - by @sxzz (a2eac)

🐞 Bug Fixes

Inline CI detection - by @sxzz (bfc64)

🏎 Performance

css: Skip renderChunk when no CSS has been collected - by @ShMcK in #967 (9f051)

View changes on GitHub

`v0.22.2`

Compare Source

🐞 Bug Fixes

Pin rolldown to minor - by @sxzz (69e78)

View changes on GitHub

`v0.22.1`

Compare Source

🚀 Features

dts: Add deps.dts option to override dependency bundling for declaration files - by @sxzz (881bf)

🐞 Bug Fixes

Improve error handling for unsupported TypeScript syntax on Node.js - by @sxzz (b93db)
Add extra space for emoji rendering in Windows Terminal - by @sxzz (925cc)
unbundle: Add shims support for unbundled builds - by @sxzz (fc991)

View changes on GitHub

`v0.22.0`

Compare Source

🚨 Breaking Changes

Drop Node.js < 22.18.0 support, make unrun optional, add tsx config loader - by @sxzz (a1042)
dts: Auto-enable dts when tsconfig declaration is true - by @sxzz in #872 (085f0)
publint: Use pkg from publint results, require publint v0.3.8+ - by @sxzz (413bb)

🚀 Features

Upgrade rolldown to 1.0.0-rc.18 - by @sxzz (66085)
Upgrade rolldown to v1.0.0 - by @sxzz (fabba)
exports: Auto-enable bin detection by default - by @sxzz in #873 (abda9)

🐞 Bug Fixes

Explicitly drop node 23 support - by @sxzz (85e65)
debug: Enhance debug logging for pack tarball - by @sxzz and Copilot (5de04)
exports: Detect types fields nested in conditional exports - by @sxzz (82fa1)
pkg: Fix duplicate configuration warning logic - by @ho991217 and @sxzz in #935 (6a0d9)

🔄 Migration Guide

Node.js version

Upgrade to Node.js 22.18.0 or later. Bun and Deno remain supported (experimental).

`unrun` is no longer bundled

If your environment relies on the unrun config loader (i.e. you're on a Node version without native TypeScript support and use the default auto loader), install it manually:

npm i -D unrun

# or, alternatively, the new tsx loader:
npm i -D tsx

If you use Node.js 22.18.0+ with native TypeScript support, no change is needed — the auto loader will pick native.

`dts` auto-enabled from tsconfig

If your tsconfig.json has compilerOptions.declaration: true but you do not want tsdown to emit .d.ts files, opt out explicitly:

// tsdown.config.ts
export default defineConfig({
  dts: false,
})

`exports.bin` auto-detection

Any entry chunk containing a shebang (e.g. #!/usr/bin/env node) now causes tsdown to write a bin field in package.json automatically. The semantics differ slightly from explicit bin: true:

Value	Single shebang	Multiple shebangs	No shebangs
(unset)	Auto-set bin	Warn, skip	Silent
`true`	Auto-set bin	Throw	Warn
`false`	No bin	No bin	No bin

To opt out entirely:

export default defineConfig({
  exports: { bin: false },
})

Links

`v0.21.10`

Compare Source

🚀 Features

Upgrade rolldown - by @sxzz (8a449)

View changes on GitHub

Configuration

📅 Schedule: (UTC)

Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
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.

bolt-new-by-stackblitz · 2025-05-12T03:23:30Z

Run & review this pull request in StackBlitz Codeflow.

pkg-pr-new · 2025-05-12T03:23:54Z

Open in StackBlitz

npm i https://pkg.pr.new/unplugin-isolated-decl@69

commit: fc27c84

socket-security · 2025-09-08T13:33:09Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm `@emnapi/runtime` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/unplugin-oxc@0.6.0` → `npm/tsdown@0.22.3` → `npm/rolldown@1.1.3` → `npm/@emnapi/runtime@1.11.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@emnapi/runtime@1.11.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

socket-security · 2025-11-19T02:27:25Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@oxc-project/types@0.138.0
	tinyglobby@0.2.17
	rolldown@1.1.3
	@typescript/native-preview@7.0.0-dev.20260630.1
	tsdown@0.22.3
	obug@2.1.3

View full report

renovate Bot added the dependencies label May 12, 2025

renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 23fd7de to 12816bf Compare May 12, 2025 10:37

renovate Bot changed the title ~~chore(deps): update all non-major dependencies~~ fix(deps): update all non-major dependencies May 12, 2025

renovate Bot force-pushed the renovate/all-minor-patch branch 15 times, most recently from be89d11 to 25010dc Compare May 20, 2025 01:23

renovate Bot changed the title ~~fix(deps): update all non-major dependencies~~ chore(deps): update dependency rolldown to v1.0.0-beta.9-commit.43425a0 May 20, 2025

renovate Bot force-pushed the renovate/all-minor-patch branch from 25010dc to 1e230c9 Compare May 20, 2025 06:20

renovate Bot changed the title ~~chore(deps): update dependency rolldown to v1.0.0-beta.9-commit.43425a0~~ fix(deps): update all non-major dependencies May 20, 2025

renovate Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from b9b2a51 to 2043e01 Compare May 22, 2025 13:43

renovate Bot force-pushed the renovate/all-minor-patch branch from 7df44ef to c5f6990 Compare June 5, 2025 07:24

renovate Bot changed the title ~~fix(deps): update all non-major dependencies~~ chore(deps): update dependency rolldown to v1.0.0-beta.9-commit.d91dfb5 Jun 5, 2025

renovate Bot force-pushed the renovate/all-minor-patch branch from c5f6990 to 442c8f9 Compare June 6, 2025 19:31

renovate Bot changed the title ~~chore(deps): update dependency rolldown to v1.0.0-beta.9-commit.d91dfb5~~ fix(deps): update all non-major dependencies Jun 6, 2025

renovate Bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from eb4ecb8 to c7e5e82 Compare June 13, 2025 17:58

renovate Bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from 6500754 to 2ab3a14 Compare June 23, 2025 01:39

chore(deps): update all non-major dependencies

fc27c84

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

chore(deps): update all non-major dependencies#69

chore(deps): update all non-major dependencies#69
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

renovate Bot commented May 12, 2025 •

edited

Loading

Uh oh!

bolt-new-by-stackblitz Bot commented May 12, 2025

Uh oh!

pkg-pr-new Bot commented May 12, 2025 •

edited

Loading

Uh oh!

socket-security Bot commented Sep 8, 2025 •

edited

Loading

Uh oh!

socket-security Bot commented Nov 19, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Uh oh!

Conversation

renovate Bot commented May 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v10.34.1: pnpm 10.34.1

Patch Changes

Platinum Sponsors

Gold Sponsors

v10.34.0: pnpm 10.34

Minor Changes

Patch Changes

Platinum Sponsors

Gold Sponsors

v10.33.4: pnpm 10.33.4

Patch Changes

Platinum Sponsors

Gold Sponsors

🚨 Breaking Changes

🐞 Bug Fixes

🏎 Performance

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🚨 Breaking Changes

🚀 Features

🐞 Bug Fixes

🔄 Migration Guide

Node.js version

unrun is no longer bundled

dts auto-enabled from tsconfig

exports.bin auto-detection

Links

🚀 Features

Configuration

Uh oh!

bolt-new-by-stackblitz Bot commented May 12, 2025

Uh oh!

pkg-pr-new Bot commented May 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Sep 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Nov 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented May 12, 2025 •

edited

Loading

`v10.34.1`: pnpm 10.34.1

`v10.34.0`: pnpm 10.34

`v10.33.4`: pnpm 10.33.4

`unrun` is no longer bundled

`dts` auto-enabled from tsconfig

`exports.bin` auto-detection

pkg-pr-new Bot commented May 12, 2025 •

edited

Loading

socket-security Bot commented Sep 8, 2025 •

edited

Loading

socket-security Bot commented Nov 19, 2025 •

edited

Loading