Repository navigation
fix(security): raise pnpm baseline to 11.11.0 - #182
Conversation
Matrix-Engage
left a comment
There was a problem hiding this comment.
Review: APPROVE — Security Tooling Baseline
Reviewed PR #182 at commit 3dd8f6c59f49392c341baec5a7babbe0a5845439.
The change consistently updates the pnpm baseline from 11.7.0 to 11.11.0 across the root package manager declaration, required CI setup and installation documentation.
The selected version addresses the reviewed vulnerable pnpm 11.x ranges. The change remains limited to development tooling and does not alter runtime, benchmark, scientific, evidence or provider behavior.
All 12 required CI jobs passed on the reviewed commit.
Recommendation: APPROVE and merge after all required repository and CODEOWNER approvals are satisfied.
After merging, verify the protected-main CI and allow Dependabot to reprocess the updated dependency state before declaring any security alerts resolved.
Related issue: #181.
Summary
Raises the repository's pnpm tooling baseline from
11.7.0to11.11.0.Current protected
mainexplicitly pins pnpm 11.7.0 in:packageManager;Public GitHub-reviewed pnpm advisories place 11.7.0 inside vulnerable 11.x ranges, including findings patched at 11.8.0 and 11.11.0. This PR moves to the smallest higher reviewed floor that clears those established ranges.
Closes #181.
Changes
package.json:pnpm@11.11.011.11.0Docs/INSTALLATION_MATRIX.md: support/CI baseline aligned to11.11.0Scope boundary
No runtime, benchmark, evidence, provider, API, scientific, or product package semantics are intentionally changed.
Security truth
The private Dependabot alert endpoint is not exposed through the current connector, so this PR does not assert an alert ID or pre-claim alert closure.
After merge, GitHub Dependency Graph / Dependabot must reprocess protected
mainbefore the Security UI state is considered resolved.