Skip to content

chore(deps): bump js-yaml and @changesets/cli - #5

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-e661dc7752
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-e661dc7752

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 12, 2026 •

Copy link
Copy Markdown

Removes js-yaml. It's no longer used after updating ancestor dependency @changesets/cli. These dependencies need to be updated together.

Removes js-yaml

Updates @changesets/cli from 2.31.1 to 3.0.1

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.1

Patch Changes

@​changesets/cli@​3.0.0

Major Changes

  • #2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

  • #2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

  • #1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

    This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

  • #1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

  • #1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

  • #2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

    This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

  • #2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

  • #2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

  • #1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

  • #1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

  • #1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

  • #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

  • #1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

  • #1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

  • #1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

  • #2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

  • #1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

    This means the CLI flows will have minor changes, but they are largely the same.

... (truncated)

Changelog

Sourced from @​changesets/cli's changelog.

3.0.1

Patch Changes

3.0.0

Major Changes

  • #2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

  • #2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

  • #1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

    This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

  • #1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

  • #1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

  • #2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

    This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

  • #2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

  • #2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

  • #1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

  • #1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

  • #1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

  • #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

  • #1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

  • #1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

  • #1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

  • #2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

  • #1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 12, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-e661dc7752 branch from 073857d to f1d08b3 Compare August 19, 2026 01:05
baabakk added a commit that referenced this pull request Aug 19, 2026
…a gate #5)

"Embedded-first" is a performance claim; this makes it a measured fact. bench/run.ts measures warm
resolve, cold resolve, promote, addVersion, and concurrent-add throughput across the embedded backends
(InMemory / SQLite / File) at two payload sizes, p50/p95/p99/mean, and writes an environment-stamped
bench/RESULTS.md. Networked backends stay env-gated (a live server), like the conformance harness.

The headline it shows: warm resolve is one label read plus a version-cache hit, so on the embedded
backends it is at Map/syscall cost (baseline: p50 ~3.6 us InMemory, ~10 us in-memory SQLite, ~176 us
File). A CI `bench-smoke` job (BENCH_QUICK) proves the harness stays runnable; the PUBLISHED numbers
come from a documented run of the built dist on fixed hardware, since a shared CI runner is too noisy.

Dev-only (bench/ is not in the package files, no changeset). The concurrent-add measure uses distinct
keys deliberately: same-key CAS contention is a correctness property proven by the conformance test,
not a throughput number, and a 50-way same-key race on one event loop is pathological, not
representative.
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-e661dc7752 branch from f1d08b3 to 96b2672 Compare August 19, 2026 19:58
Removes [js-yaml](https://github.com/nodeca/js-yaml). It's no longer used after updating ancestor dependency [@changesets/cli](https://github.com/changesets/changesets/tree/HEAD/packages/cli). These dependencies need to be updated together.


Removes `js-yaml`

Updates `@changesets/cli` from 2.31.1 to 3.0.1
- [Release notes](https://github.com/changesets/changesets/releases)
- [Changelog](https://github.com/changesets/changesets/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/changesets/changesets/commits/@changesets/cli@3.0.1/packages/cli)

---
updated-dependencies:
- dependency-name: "@changesets/cli"
  dependency-version: 3.0.0
  dependency-type: direct:development
- dependency-name: js-yaml
  dependency-version:
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-e661dc7752 branch from 96b2672 to 01aad53 Compare August 19, 2026 20:11
baabakk added a commit that referenced this pull request Aug 19, 2026
…ments (beta gate #5)

Closes the benchmark half of the evidence gate. Every cloud row ran the same portable script against the
PUBLISHED npm package rather than a local build, so the figures describe what a consumer installs.

Warm resolve p50, InMemory, 16 B payload:

  AWS Lambda arm64            0.98us      <- serverless, and no network call to get there
  AWS EC2 c7a (AMD Genoa)     1.93us
  Hetzner CCX13 (EPYC Milan)  1.97us
  AWS EC2 c7g (Graviton3)     2.67us
  AWS EC2 c7i (Sapphire Rap.) 3.55us
  Hetzner CX23 (Xeon Skylake) 3.78us
  Android phone (Termux)      10.21us
  Windows laptop              13.0us      <- noisiest; documented as such

Three findings worth keeping. A cold Lambda is configured in ~339us having made NO network call, because
the code default is compiled into the bundle; that is a difference in kind from a config service, not a
difference in latency. The same-generation EC2 trio isolates the vendor and puts AMD ~1.8x ahead of Intel,
with the two Intel rows landing within 6% of each other across seven years of silicon and two providers,
which is a good consistency check on the harness. And the phone beats the laptop on both median and tail,
which is a caution about reading any of these rows without knowing what else the machine was doing.

The write-up states its caveats plainly: the laptop row is noisy by construction, File-backend figures track
the filesystem more than the CPU, iteration counts auto-calibrate, and these are single runs establishing
orders of magnitude rather than a basis for 5% comparisons.
baabakk added a commit that referenced this pull request Aug 20, 2026
…dvisory

Closes the two HIGH Dependabot alerts that have been reported on every push. The vulnerability is a
quadratic-CPU parse in js-yaml, which reached us only transitively through @changesets/cli; changesets
3.x drops it entirely. Worth stating precisely: js-yaml was a DEVELOPMENT dependency of the release
toolchain and never shipped, because the published packages have no runtime dependencies at all. No
consumer was ever exposed. `npm audit` now reports 0 vulnerabilities.

Applied directly on main rather than by merging Dependabot's PR #5, which was raised on 2026-08-12 and
predates the typedoc, pg, and ioredis devDependencies added since; merging its lockfile would have
regressed them.

Every breaking change in 3.0 was checked against this repo before upgrading. Not applicable: the
`changeset tag` rename (we use `changeset publish`), the `prettier` config option removal (we never set
it), and the Yarn Classic removal (we use npm). Satisfied: npm >= 10.9 and the Node floor. Applicable
and verified: prerelease changesets now live in `.changeset/pre/` rather than accumulating in the root
with their ids tracked in pre.json, and the documented auto-migration ran cleanly, moving all twelve
consumed changesets and reducing pre.json to mode and tag. Nothing was lost, and pre mode still reports
the beta line correctly.

Verified after: build clean, typecheck clean, 238 tests green, docs generate with no warnings, and the
dist-tag reconciler still reads the published state correctly.
@baabakk

baabakk commented Aug 20, 2026

Copy link
Copy Markdown
Owner

Applied directly on main in f2df45c rather than merging this branch.

The upgrade itself is exactly what this PR proposed (@changesets/cli 2.31.1 to 3.0.1, dropping js-yaml and its quadratic-parse advisory), and npm audit now reports 0 vulnerabilities.

The reason for not merging the branch: it was raised on 2026-08-12 and predates the typedoc, pg, and ioredis devDependencies added since, so its lockfile would have regressed them.

Each 3.0 breaking change was checked against this repo first. The changeset tag rename does not apply (this repo uses changeset publish), the prettier config option was never set here, and Yarn Classic was never used. The one that did apply is the move of prerelease changesets into .changeset/pre/; the documented auto-migration ran cleanly, relocating all twelve consumed changesets and reducing pre.json to mode and tag, with nothing lost. Build, typecheck, 238 tests, and the docs build were all verified green afterwards, as was the dist-tag reconciler.

Thanks Dependabot.

@baabakk baabakk closed this Aug 20, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 20, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available.

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/multi-e661dc7752 branch August 20, 2026 05:28
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