Skip to content

Bump taze from 19.6.0 to 19.7.0#5

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/taze-19.7.0
Closed

Bump taze from 19.6.0 to 19.7.0#5
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/taze-19.7.0

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Oct 20, 2025

Bumps taze from 19.6.0 to 19.7.0.

Release notes

Sourced from taze's releases.

v19.7.0

   🚀 Features

    View changes on GitHub
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [taze](https://github.com/antfu-collective/taze) from 19.6.0 to 19.7.0.
- [Release notes](https://github.com/antfu-collective/taze/releases)
- [Commits](antfu-collective/taze@v19.6.0...v19.7.0)

---
updated-dependencies:
- dependency-name: taze
  dependency-version: 19.7.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 20, 2025
@socket-security-staging
Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​taze@​19.6.0 ⏵ 19.7.096 +110010096 +2100

View full report

@socket-security
Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​taze@​19.6.0 ⏵ 19.7.097 +110010096 +1100

View full report

@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github Oct 20, 2025

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/taze-19.7.0 branch October 20, 2025 19:57
John-David Dalton (jdalton) added a commit that referenced this pull request Apr 18, 2026
…n-parser exports

Org-scan R4 #5: src/utils/ contained only get-ipc.ts, giving IPC two homes
(src/ipc.ts + src/utils/get-ipc.ts). Moved to src/ipc-cli.ts (ipc-* sibling
of existing ipc.ts), deleted the empty src/utils/ directory. The file is
Socket-CLI-specific env-var IPC; updated fileoverview to point at the
complementary stub IPC module. Test moved to test/unit/ipc-cli.test.mts.

Org-scan R4 #6: validation/json-parser exported 6 functions; 5 had zero
internal callers and zero sibling-repo (socket-cli/registry/sdk-js/etc)
callers confirmed by grep. Deleted createJsonParser, parseJsonWithResult,
parseNdjson, streamNdjson, tryJsonParse + their tests + the JsonParseResult
type. Kept safeJsonParse (core function, matches module name).

Public export changes:
- package.json: renamed ./utils/get-ipc → ./ipc-cli
- dropped 5 dead json-parser exports (surface narrows, no sibling breakage)
John-David Dalton (jdalton) added a commit that referenced this pull request May 7, 2026
…-test exclusions

Push #5 — 92% → 95% via two complementary moves:

5A: c8 ignore mop-up for unreachable-on-this-runner branches
- bin.ts findRealNpm fallback (only fires when npm isn't at any
  common path; test runners always have npm) and stale-cache eviction
  (only fires when a cached binary is removed mid-session).
- process-lock.ts exit-handler body — only fires on real process exit.
- agent.ts execScript no-lockfile fallback — findUpSync walks
  ancestors, so a clean tmpdir test is fragile when CI runners have
  a lockfile at the workspace root.
- paths/normalize.ts isWindowsDeviceRoot + drive-letter detection +
  fromUnixPath backslash conversion — all Windows-only.

5B: integration-test exclusions in vitest.config.mts
Three files require a live npm registry / Arborist resolution to
test meaningfully — unit-test mocking would just verify the mocks,
not the real behavior. Excluded from coverage with documented
rationale:
- src/dlx/arborist.ts (Arborist wrapper, 100% external delegation)
- src/dlx/lockfile.ts (generatePackagePin: Arborist + httpDownload)
- src/dlx/package.ts (dlxPackage: Arborist install + Firewall API)
- src/dlx/binary.ts (dlxBinary: full http download + extract + cache)

The pure helpers in those files (parsePackageSpec, npmPurl,
findBinaryPath, executePackage, makePackageBinsExecutable,
downloadBinaryFile, executeBinary, getBinaryCacheMetadataPath) ARE
already unit-tested in their own *-pure.test.mts files; the
exclusion only removes the orchestration layer that needs real
external systems.

Project: 92.17% → 95.03% lines, 83.14% → 86.35% branches, 96.27% →
97.88% functions across 6949 passing tests.

.config/vitest.config.mts thresholds bumped 92/83/96 → 95/86/97.
README coverage badge bumped 92% → 95%.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant