Skip to content

chore(deps): bump pprof-format to 2.3.1 - #393

Merged
szegedi merged 1 commit into
mainfrom
szegedi/bump-pprof-format-2.3.1
Aug 11, 2026
Merged

chore(deps): bump pprof-format to 2.3.1#393
szegedi merged 1 commit into
mainfrom
szegedi/bump-pprof-format-2.3.1

Conversation

@szegedi

@szegedi szegedi commented Aug 11, 2026

Copy link
Copy Markdown

Moves pprof-format from ^2.3.0 to ^2.3.1 and repins the lockfile.

What is actually in 2.3.1

Diffing the published tarballs, package.json is the only file that differs:

$ diff -rq pprof-format-2.3.0/package pprof-format-2.3.1/package
Files a/package/package.json and b/package/package.json differ

and within it: the version, two devDependency bumps (@types/node, eslint), and an overrides block pinning brace-expansion and linkify-it in pprof-format's own dev tree.

pprof-format has no runtime dependencies, and a dependency's overrides are 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.0 already 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 in package.json, and the version/resolved/integrity triple plus the dependency spec in package-lock.json. Nothing else in the lock moved.

Verification

Full suite 115 passing, gts check 0 errors, addon builds clean.

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.
@github-actions

Copy link
Copy Markdown

Overall package size

Self size: 2.49 MB
Deduped: 3.19 MB
No deduping: 3.19 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

@IlyasShabi IlyasShabi added the semver-patch Bug or security fixes, mainly label Aug 11, 2026
@datadog-prod-us1-3

This comment has been minimized.

@szegedi
szegedi merged commit 93531f4 into main Aug 11, 2026
70 of 71 checks passed
@szegedi
szegedi deleted the szegedi/bump-pprof-format-2.3.1 branch August 11, 2026 09:54
@szegedi szegedi mentioned this pull request Aug 11, 2026
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver-patch Bug or security fixes, mainly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants