chore(deps): bump pprof-format to 2.3.1 - #393
Merged
Merged
Conversation
Note this is a metadata-only release: diffing the published 2.3.0 and 2.3.1 tarballs, package.json is the only file that differs. pprof-format has no runtime dependencies, and 2.3.1 carries a version bump, two devDependency bumps, and an `overrides` block patching brace-expansion and linkify-it in its own dev tree. A dependency's `overrides` are ignored by npm — only the root project's apply — so none of that reaches consumers. So this changes no shipped code and fixes no vulnerability we are exposed to. It keeps us on the current release and off tooling's "behind latest" reports, which is the whole of it. `^2.3.0` already admitted 2.3.1, so the substantive part is the lockfile pin; the range is moved in step so the declared floor matches what we test against. Suite: 115 passing.
szegedi
requested review from
IlyasShabi,
nsavoire and
r1viollet
as code owners
August 11, 2026 09:40
IlyasShabi
approved these changes
Aug 11, 2026
Overall package sizeSelf size: 2.49 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | pprof-format | 2.3.1 | 504.33 kB | 504.33 kB | | source-map | 0.8.0 | 185.66 kB | 185.66 kB | | node-gyp-build | 4.8.4 | 13.86 kB | 13.86 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
This comment has been minimized.
This comment has been minimized.
Merged
szegedi
added a commit
that referenced
this pull request
Aug 11, 2026
Note this is a metadata-only release: diffing the published 2.3.0 and 2.3.1 tarballs, package.json is the only file that differs. pprof-format has no runtime dependencies, and 2.3.1 carries a version bump, two devDependency bumps, and an `overrides` block patching brace-expansion and linkify-it in its own dev tree. A dependency's `overrides` are ignored by npm — only the root project's apply — so none of that reaches consumers. So this changes no shipped code and fixes no vulnerability we are exposed to. It keeps us on the current release and off tooling's "behind latest" reports, which is the whole of it. `^2.3.0` already admitted 2.3.1, so the substantive part is the lockfile pin; the range is moved in step so the declared floor matches what we test against. Suite: 115 passing. (cherry picked from commit 93531f4)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves
pprof-formatfrom^2.3.0to^2.3.1and repins the lockfile.What is actually in 2.3.1
Diffing the published tarballs,
package.jsonis the only file that differs:and within it: the version, two devDependency bumps (
@types/node,eslint), and anoverridesblock pinningbrace-expansionandlinkify-itin pprof-format's own dev tree.pprof-formathas no runtime dependencies, and a dependency'soverridesare ignored by npm — only the root project's apply. So no shipped code changes here, and no vulnerability we are exposed to is fixed. It keeps us on the current release and off tooling's "behind latest" reports; that is the whole of it. Flagging it so nobody reads the CVE-shaped commit titles upstream and assumes otherwise.^2.3.0already admitted 2.3.1, so the substantive part is the lockfile pin. The range moves in step so the declared floor matches what CI tests against.Diff scope
Confined to
pprof-format: one line inpackage.json, and the version/resolved/integrity triple plus the dependency spec inpackage-lock.json. Nothing else in the lock moved.Verification
Full suite 115 passing,
gts check0 errors, addon builds clean.