Repository navigation
[WRONG BRANCH] fix(deps): pin zod/body-parser for 2.92.0 audit:high republish - #7643
Conversation
GHSA-mrhx-c7xc-m3w5 and GHSA-27r3-jxmh-p828 blocked the 2.92.0 publish. Leave the package version at 2.92.0 so Release can republish that version. Co-authored-by: JUN <jun@lidgeai.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
✅ Deterministic PR hygiene checks passed. |
⏳ DRAFT
What to do
Its title has been prefixed with |
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
⛔ Files ignored due to path filters: 1
📒 Files selected for processing: 2
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
#7942) * release: v2.33.0-preview.20260825 * release: v2.34.0-preview.20260827 * release: v2.36.0-preview.20260829 * fix(release): pass the bump job's permissions through the reusable-workflow call (#3262) Both v2.40.0 release dispatches (33615174183 preview, 33615177849 main) died at startup_failure: a workflow_call cannot grant its callee more than the calling job holds, and dev-version-bump.yml's job declares contents+pull- requests write. #3129 wired the call but never dispatched a release, so this is its first live run. The caller job now declares exactly the callee's two permissions; no other job in release.yml gains anything. Co-authored-by: jun <jun@lidge.dev> (cherry picked from commit 7ce0ba5) * release: set preview channel version 2.48.0-preview.20260908 * release: set main channel version 2.48.0 * chore(release): promote 2.55.0-preview.20260914 to preview Promotes the dev product snapshot 62f0222 to the preview train. The 2.55.0 line carries the #4546 cost-guard work: one send budget per logical request with a shared final-recovery reserve, zero-is-zero refusals with a typed error rather than a synthetic 502, compact and the Kiro inner retries admitted against that budget, a finite send ceiling per root workflow with an interactive reserve a fan-out cannot take, and a healthy detour promoted on transient-hold expiry instead of released cold. The previous preview tip 2.54.0-preview.20260914 is already tagged and published and is outranked by v2.54.0, so it could not be re-released; this is a new candidate rather than a re-cut. * chore(release): promote the verified 2.55.0 product tree to main Same product tree as preview 7bdd1b2 / 2.55.0-preview.20260914, which published successfully with its registry smoke green. Only package.json version differs. * ci(release): expose Linux bundler diagnostics for stable artifacts * fix(release): prepare stable platform bundles * fix(desktop): carry native sidecar packaging repair to main (#5532) * chore(ci): refresh main release verification (#5534) * fix(release): carry lipo argument fix to main (#5537) * fix(release): carry checksum and signature repair to main (#5546) * fix(release): carry Windows checksum record support to main (#5552) * fix(release): publish the GitHub release only after its verified assets attach (#5555) (#5558) GitHub freezes a release when it is published, so the attach step's upload came back HTTP 422 "Cannot upload assets to an immutable release". Every release from v2.55.0 to v2.60.0 therefore shipped with zero assets and the desktop updater had nothing to download. Create the release as a draft and flip it to published in attach-release, after the verified bundle is uploaded. Release notes still come from the validated notes file written at creation. * release: prepare 2.63.0 version metadata (#5612) * release: prepare 2.69.0 version metadata * fix(release): sign the packaged macOS keyring addons before notarization (#6271) * fix(release): sign the packaged macOS keyring addons before notarization Notarization rejected the 2.73.0 preview app: Resources/keyring/*.node, bundled since #6161, were unsigned or ad-hoc and had no secure timestamp, and Tauri does not sign files under Resources. Sign each darwin addon in place with the Developer ID identity, hardened runtime and timestamp after the certificate import and before tauri build, verify the result, and fail a real release that lacks signing material. * fix(release): match keyring signature fields without a pipe (cherry picked from commit 11782ee) * chore(release): 2.74.0 * fix(deps): bump proxy-addr, fast-uri, ip-address and source-map-js for new advisories release.yml's dependency audit refused 2.79.0 on a critical advisory published after the candidate was cut: proxy-addr <2.0.8 is vulnerable to IP spoofing via IPv4-mapped IPv6 trust subnets (GHSA-jqcg-44mw-7w3h), reached through @modelcontextprotocol/sdk > express. gui/ reports source-map-js <1.2.2 (GHSA-68fv-2mgg-jv7q, vite > postcss). bun audit fix, lockfiles only, every bump inside its declared range: proxy-addr 2.0.7 -> 2.0.8, fast-uri 3.1.7 -> 3.1.8, ip-address 10.4.0 -> 10.7.1, and in gui/ source-map-js 1.2.1 -> 1.2.2. Both audits now report no vulnerabilities at --audit-level=high. * fix(deps): bump @modelcontextprotocol/sdk to 1.31.0 for GHSA-6qxp-vccf-f47h * fix(deps): clear high-severity audit findings blocking the 2.90.0 release (#7481) Raise @modelcontextprotocol/sdk to ^1.32.1 (GHSA-22jm-h49p-29qw, GHSA-46jr-4wx8-v453) and lock gui vite at 8.2.4 (GHSA-587h-7wmj-h5pm). release.yml runs bun run audit:high before publishing, and both advisories made it fail. * fix(deps): pin zod 4.6.6 and body-parser 2.4.0 for 2.92.0 (#7643) GHSA-mrhx-c7xc-m3w5 and GHSA-27r3-jxmh-p828 blocked the 2.92.0 publish. Leave the package version at 2.92.0 so Release can republish that version. Co-authored-by: Cursor Agent <cursoragent@cursor.com> * fix(deps): bump gui happy-dom to 21.0.4 for GHSA-834v-8h66-3h79 (2.92.0) (#7645) Co-authored-by: lidge-jun <243035832+lidge-jun@users.noreply.github.com> * build(deps): bump rustls from 0.23.45 to 0.23.46 in /desktop/src-tauri Bumps [rustls](https://github.com/rustls/rustls) from 0.23.45 to 0.23.46. - [Release notes](https://github.com/rustls/rustls/releases) - [Changelog](https://github.com/rustls/rustls/blob/main/CHANGELOG.md) - [Commits](rustls/rustls@v/0.23.45...v/0.23.46) --- updated-dependencies: - dependency-name: rustls dependency-version: 0.23.46 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: JUN <bitkyc08@gmail.com> Co-authored-by: jun <jun@junui-MacBookPro.local> Co-authored-by: jun <jun@lidge.dev> Co-authored-by: lidge-jun <243035832+lidge-jun@users.noreply.github.com> Co-authored-by: t <a@b.com> Co-authored-by: JUN <jun@lidgeai.com> Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: lidge-jun <lidge-jun@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Epinephrine <luvs01@hanmail.net>
Summary
Applies the same
audit:highpins that landed ondevin #7642 ontomain, so Release can republish 2.92.0. The 2.92.0 publish failed at the high-severity dependency audit (release run 40031662901, #7638).zodpin:4.4.3→ exact4.6.6(GHSA-mrhx-c7xc-m3w5, patched in>=4.6.6). npm latest is4.6.7; that tag is only a version-constant bump, so this stays on the advisory floor, matching fix(deps): pin zod 4.6.6 and body-parser 2.4.0 for audit:high #7642.body-parser: exact2.4.0(GHSA-27r3-jxmh-p828), added beside the existing overrides.@hono/node-server,fast-uri,hono,ip-address, andqsare unchanged.body-parserstays transitive through@modelcontextprotocol/sdk→express@5.2.1.bun.lockresolveszod@4.6.6,body-parser@2.4.0, nestedcontent-type@2.1.0, and nestediconv-lite@0.7.3. The lockfile hunk matches fix(deps): pin zod 4.6.6 and body-parser 2.4.0 for audit:high #7642. The existingqs: ^6.16.0override still resolvesqs@6.16.0even though body-parser 2.4.0 declaresqs@^6.16.1(already filed as [Bug]: qs override keeps 6.16.0 under body-parser 2.4.0's ^6.16.1 #7641).package.jsonversionstays 2.92.0.tests/ci-workflows/install-scripts.test.tsexpects the new zod pin, the same one-line expectation update as fix(deps): pin zod 4.6.6 and body-parser 2.4.0 for audit:high #7642.This pull request targets
mainbecausedevis already2.93.0and already contains these pins. Republishing 2.92.0 has to move the release branch.Class C4 (release gate and supply chain). PABCD: the plan copied only the #7642 advisory floors; the resulting
bun.lockdiff is the same hunk as that commit.Closes #7638
Already filed, and left unchanged here:
Verification
bun run audit:highexit 0. Root:No vulnerabilities found (checked 144 packages, 2 below --audit-level=high). GUI:No vulnerabilities found (checked 82 packages).bun run typecheck(bun x tsc --noEmit) exit 0.bun test tests/ci-workflows/install-scripts.test.ts: 10 pass, 0 fail.bun run testwas not run. The diff is the two pins, the lockfile, and one expectation string; nosrc/change. CI covers the suite.Head:
ef31e2e655d4af66e48517e8bd850bc95ebba646Checklist