Refresh JS dependencies within their current ranges #25

Merged
matchu merged 1 commit from armin-bot/impress:claude/yarn-up into main 2026-11-15 19:08:41 -08:00
Contributor

Regenerates yarn.lock so every package, direct and transitive, resolves to the newest version its existing range allows. package.json is 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

  • @apollo/client 3.10.1 → 3.13.9
  • @tanstack/react-query 5.32 → 5.105
  • @emotion/react 11.14.0, @emotion/styled 11.14.1
  • graphql 15.10.3, @loadable/component 5.16.7
  • Tooling: esbuild 0.25.12, typescript 5.9.3, prettier 3.9, @typescript-eslint 7.18, eslint 8.57.1, newer eslint plugins
  • bin/neopass-server deps: express 4.22.3, oauth2-mock-server 7.2.1

Apollo 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:

  • connectToDevTools
  • onError / onCompleted on useQuery

Those 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's postinstall was 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.
  • The peer-dependency warnings from yarn install (Chakra 1 wanting React 16/17) are unchanged.

Testing

  • yarn install --immutable, yarn dedupe --check, yarn build, yarn lint and prettier --check all pass.
  • rspec passes.
  • bin/security-scan reports no stale ignores.
  • NeoPass works against 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:

  1. Load a Blue Acara wearing an item
  2. Search "hat" and wear a result
  3. Clear the search
  4. Open the pose picker, pick Sad, and open the Styles tab
  5. Switch species to Aisha
  6. Reload

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):

Outfit loaded Wearing a search result
Loaded Wear
Pose picker, Styles tab Switched to Aisha; Acara hat flagged incompatible
Styles Species

🤖 Generated with Claude Code

https://claude.ai/code/session_014PWWd1Ljyt9gAxzYFpJgJx

Regenerates `yarn.lock` so every package, direct and transitive, resolves to the newest version its existing range allows. `package.json` is 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 - @apollo/client 3.10.1 → 3.13.9 - @tanstack/react-query 5.32 → 5.105 - @emotion/react 11.14.0, @emotion/styled 11.14.1 - graphql 15.10.3, @loadable/component 5.16.7 - Tooling: esbuild 0.25.12, typescript 5.9.3, prettier 3.9, @typescript-eslint 7.18, eslint 8.57.1, newer eslint plugins - `bin/neopass-server` deps: express 4.22.3, oauth2-mock-server 7.2.1 **Apollo 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: - `connectToDevTools` - `onError` / `onCompleted` on `useQuery` Those 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's `postinstall` was 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. - The peer-dependency warnings from `yarn install` (Chakra 1 wanting React 16/17) are unchanged. ## Testing - `yarn install --immutable`, `yarn dedupe --check`, `yarn build`, `yarn lint` and `prettier --check` all pass. - rspec passes. - `bin/security-scan` reports no stale ignores. - NeoPass works against `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: 1. Load a Blue Acara wearing an item 2. Search "hat" and wear a result 3. Clear the search 4. Open the pose picker, pick Sad, and open the Styles tab 5. Switch species to Aisha 6. Reload 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): | Outfit loaded | Wearing a search result | |---|---| | ![Loaded](https://code.openneo.net/attachments/2b6744da-c035-4011-8ed6-32acc8fa091f) | ![Wear](https://code.openneo.net/attachments/e12304b6-685d-4681-a253-5afe5ea49192) | | **Pose picker, Styles tab** | **Switched to Aisha; Acara hat flagged incompatible** | | ![Styles](https://code.openneo.net/attachments/12481623-3f29-4172-bcf3-340c16420fac) | ![Species](https://code.openneo.net/attachments/dd18b2f7-3442-42e0-9d88-bd5e74062f3c) | 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_014PWWd1Ljyt9gAxzYFpJgJx
Refresh JS dependencies within their current ranges
All checks were successful
CI / rspec (pull_request) Successful in 11m31s
CI / deploy (pull_request) Has been skipped
2cafd0f05c
Regenerate yarn.lock so every package, direct and transitive, resolves to
the newest version its existing range allows. package.json is unchanged,
so no major upgrades. Notable direct moves:

- @apollo/client 3.10.1 -> 3.13.9, @tanstack/react-query 5.32 -> 5.105,
  @emotion/react 11.14.0, @emotion/styled 11.14.1, graphql 15.10.3,
  @loadable/component 5.16.7
- Tooling: esbuild 0.25.3 -> 0.25.12, typescript 5.4 -> 5.9.3,
  prettier 3.2 -> 3.9, @typescript-eslint 7.18, eslint 8.57.1, and
  newer eslint plugins
- bin/neopass-server deps: express 4.22.3, oauth2-mock-server 7.2.1

@apollo/client is held at 3.13.9 rather than 3.14.x. 3.14 is the bridge
release to Apollo 4, and logs deprecation warnings in the browser console
for options we use (connectToDevTools, and onError/onCompleted on
useQuery). Those are better handled along with the Apollo 4 upgrade.

As a supply-chain precaution, nothing in the lockfile is younger than 14
days. Versions published more recently than that (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's postinstall was already there).

The update fixes 41 of the advisories in .security-scan-ignore.yml (the
@babel/runtime and yaml ones, plus the dev-only express, body-parser,
qs, js-yaml, brace-expansion and glob-library ones), so remove those
entries. The react-router and minimatch GHSA-g3hv-75wg-m249 ones remain.

Prettier 3.9 indents a comment inside a multi-line `||` expression
differently, so reformat the one file that has one.

The peer dependency warnings from `yarn install` (Chakra 1 wanting
React 16/17) are unchanged from before.

Tested: `yarn install --immutable`, `yarn build` and `yarn lint` pass,
rspec passes, and bin/security-scan reports no stale ignores. NeoPass
login against bin/neopass-server still works.

For the wardrobe, I loaded production impress.openneo.net (logged out)
with its wardrobe bundle swapped for local builds of the old and new
lockfiles. Loading an outfit, searching items, wearing one, picking a
pose, opening the Styles tab, changing species, and reloading all behave
the same: the screenshots at each step are pixel-identical, and the
console output matches.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014PWWd1Ljyt9gAxzYFpJgJx
matchu merged commit dfea805f5e into main 2026-11-15 19:08:41 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OpenNeo/impress!25
No description provided.