fix(deps): patch undici, js-yaml and brace-expansion advisories - #177
Merged
FranDisalvo90 merged 1 commit intoJul 22, 2026
Merged
Conversation
The strict supply-chain audit that gates the release job has been failing
since 0.89.0, so no publish has gone out — 15 vulnerabilities, all reaching
us through dev-only tooling. `pnpm audit --prod` is clean, so nothing here
affects the published package or its consumers.
New/raised overrides, all following the existing exact-version policy:
undici → 6.27.0 / 7.28.0 (first override; arrives via the
@semantic-release/github client and @semantic-release/npm
through @actions/core > @actions/http-client)
js-yaml → 4.3.0 for GHSA-52cp-r559-cp3m
brace-expansion → 1.1.16 / 2.1.2 / 5.0.7 for GHSA-3jxr-9vmj-r5cp, which
applies to all three majors in their own ranges
`pnpm audit:supply-chain` now exits 0 with no known vulnerabilities and all
688 registry signatures verified.
cernadasjuan
approved these changes
Jul 22, 2026
pluggy-github-app Bot
pushed a commit
that referenced
this pull request
Jul 22, 2026
# [0.90.0](v0.89.0...v0.90.0) (2026-07-22) ### Bug Fixes * **account:** rename ReservedBalance.amounts to availableAmounts ([#176](#176)) ([a763c24](a763c24)) * **deps:** patch undici, js-yaml and brace-expansion advisories ([#177](#177)) ([85ececd](85ececd)) ### Features * **cc:** adding cc bill dates ([#175](#175)) ([1a60c64](1a60c64))
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
2 participants
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.
Summary
The strict supply-chain audit that gates the release job has been failing since 0.89.0, so no publish has gone out — the last two merges (
#175,#176) are sitting onmasterunreleased. 15 vulnerabilities, all reaching us through dev-only tooling.pnpm audit --prodis clean, so none of this affects the published package or anyone installing it. The gate was blocking releases over vulnerabilities in the release tooling itself.New / raised overrides, all following the existing exact-version policy:
undici@66.27.0undici@77.28.0js-yaml4.2.04.3.0brace-expansion@11.1.141.1.16brace-expansion@22.0.32.1.2brace-expansion@55.0.65.0.7undicihad no override before — it arrives through the@semantic-release/githubclient and through@semantic-release/npmvia@actions/core > @actions/http-client. GHSA-3jxr-9vmj-r5cp applies to all threebrace-expansionmajors in their own ranges, not just 5.x.All pinned versions are ≥14 days old, so they satisfy
minimumReleaseAge.Test plan
pnpm audit:supply-chain— exits 0, "No known vulnerabilities found", 688 packages with verified registry signatures (was: 15 vulnerabilities, 4 low / 3 moderate / 8 high)pnpm audit --prod— clean before and after, confirming no consumer impactpnpm test— 56/56 passpnpm buildcleanpnpm install --frozen-lockfilesucceedspnpm exec eslint .clean