Repository navigation
chore: bump astro, fast-xml-parser and minimatch past security advisories - #246
Conversation
…ries Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
Dependabot flagged open advisories for astro (fixed in 7.4.7), fast-xml-parser (fixed in 5.12.0) and minimatch (7.x to 11.0.0, fixed in 11.0.1). Its own PRs could not land: #226 only touched package.json without the lockfile, and #232 conflicted on the lockfile.
apps/marketing: astro^7.3.5to^7.4.7(resolves 7.4.13). The marketing build passes.apps/web: fast-xml-parser5.7.3to5.12.0. The file preview tests that cover XML parsing pass.pnpm-workspace.yaml: overrideminimatch@>=7 <11.0.1to11.0.9. There is no patched 9.x or 10.x, and 11 keeps the same exports and engines. The affected copies came in through electron packaging (@electron/asar,@electron/universal) and@expo/fingerprint.Supersedes #226 and #232.