Refresh JS dependencies within their current ranges #25
Loading…
Reference in a new issue
No description provided.
Delete branch "armin-bot/impress:claude/yarn-up"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Regenerates
yarn.lockso every package, direct and transitive, resolves to the newest version its existing range allows.package.jsonis unchanged, so there are no major upgrades. This one is independent of #23 / #24, and the branches don't touch the same files.What moves
bin/neopass-serverdeps: express 4.22.3, oauth2-mock-server 7.2.1Apollo is held at 3.13.9, not 3.14.x. 3.14 is the bridge release to Apollo 4. It logs deprecation warnings in the browser console, production included, for options we use:
connectToDevToolsonError/onCompletedonuseQueryThose are better handled along with the Apollo 4 upgrade.
Supply-chain cooldown: nothing in the lockfile is younger than 14 days. Fresher versions (babel, semver, brace-expansion, prettier, react-query and a few others) are held back to their newest older release via
yarn set resolution. No newly added package has install scripts; esbuild'spostinstallwas already there.Other
.security-scan-ignore.yml: removes the 41 entries this update fixes: @babel/runtime, yaml, and the dev-only express/body-parser/qs/js-yaml/brace-expansion/glob-library ones. Still ignored: the two react-router entries and minimatch GHSA-g3hv-75wg-m249.HTML5Badge.js: Prettier 3.9 indents a comment inside a multi-line||differently, so this file is reformatted.yarn install(Chakra 1 wanting React 16/17) are unchanged.Testing
yarn install --immutable,yarn dedupe --check,yarn build,yarn lintandprettier --checkall pass.bin/security-scanreports no stale ignores.bin/neopass-server.Wardrobe QA against production data
I loaded production impress.openneo.net, logged out and read-only. Playwright swapped its wardrobe bundle for local builds of the old and new lockfiles, and I ran the same flow on each:
Every step behaved the same on both builds. The screenshots at all 9 checkpoints are pixel-identical between old and new, and the console output is the same set of pre-existing React warnings.
Screenshots from the new build (old is identical):
🤖 Generated with Claude Code
https://claude.ai/code/session_014PWWd1Ljyt9gAxzYFpJgJx