Repository navigation
chore(deps): bump react and @types/react in /frontend - #332
Closed
dependabot[bot] wants to merge 4 commits into
Closed
dependabot[bot] wants to merge 4 commits into
dependabot[bot] wants to merge 4 commits into
Conversation
Bumps [react](https://github.com/react/react/tree/HEAD/packages/react) and [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react). These dependencies needed to be updated together. Updates `react` from 18.3.1 to 19.3.1 - [Release notes](https://github.com/react/react/releases) - [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/react/react/commits/v19.3.1/packages/react) Updates `@types/react` from 18.3.31 to 19.3.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react) --- updated-dependencies: - dependency-name: react dependency-version: 19.3.1 dependency-type: direct:production update-type: version-update:semver-major - dependency-name: "@types/react" dependency-version: 19.3.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
This was referenced Nov 14, 2026
hyperpolymath
added a commit
that referenced
this pull request
Nov 14, 2026
…ript 5 and 7 (#342) ## Change and reason Dependabot's TypeScript 7.0.2 bump (#336) fails the frontend build: `tsc` reports TS2503 "Cannot find namespace 'Plotly'" in `frontend/src/figure/FigureEditor.tsx` and `frontend/src/figure/export.ts`. The failure is real, not a CI fault. Both files used `Plotly.Data` and `Plotly.Layout` through the global namespace that `@types/plotly.js` declares, which TypeScript 7 no longer resolves. They now import `Data` and `Layout` from `plotly.js` as types. The fix works on the current TypeScript 5.9.3 as well, so it can merge before the bump. ## Validation - Reproduced the three errors with TypeScript 7.0.2 against `main`. - After the change: `tsc` is clean on 7.0.2 and on 5.9.3, `bun run build` passes, `bun test src` gives 90 pass, 0 fail. - Not run: the Julia and R jobs (this change touches two frontend files only). CI on this PR covers them. ## Scope Two files, type imports only, no runtime change, no lockfile change. The other Dependabot bumps (#333, #334, #335, #332) are separate and not touched here. ## Contribution checks - [x] I followed CONTRIBUTING.md. - [x] This branch starts at current main (a056c6e). - [ ] CI has run and passes. - [x] Existing licensing, citation and acknowledgement text is unchanged. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZkJwTENF5faco36Cn5)_ Co-authored-by: Claude <noreply@anthropic.com>
hyperpolymath
added a commit
that referenced
this pull request
Nov 14, 2026
…n Vite 6 and 8 (#343) ## Change and reason Dependabot's Vite 8.3.7 bump (#335) fails the frontend build in the Julia tests job: `TypeError: manualChunks is not a function`. Vite 8 builds with Rolldown, which rejects the object form of `build.rollupOptions.output.manualChunks` that `frontend/vite.config.ts` used. The failure is real, not a CI fault. The config now uses the function form, which Rollup (Vite 6) and Rolldown (Vite 8) both accept, and it produces the same `plotly` chunk. ## Validation - Reproduced the failure from the #335 job log (Vite 8.3.7, `tsc` passes, then the build fails at the config). - After the change: `bun run build` passes on the current Vite 6.4.5 and on Vite 8.3.7 in a scratch copy; both emit a `plotly-*.js` chunk. - Not run: the Julia and R jobs (this change touches one frontend config file). CI on this PR covers them. Vite 8's warning about `@vitejs/plugin-react` 4.x is not addressed here; #333 is the plugin bump. ## Scope One file, no lockfile change, no runtime change. The other Dependabot bumps (#332, #333, #334, #336) are separate; #336 is fixed by #342. ## Contribution checks - [x] I followed CONTRIBUTING.md. - [x] This branch starts at current main (a056c6e). - [ ] CI has run and passes. - [x] Existing licensing, citation and acknowledgement text is unchanged. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZkJwTENF5faco36Cn5)_ Co-authored-by: Claude <noreply@anthropic.com>
hyperpolymath
enabled auto-merge (squash)
November 16, 2026 21:08
hyperpolymath
self-requested a review
November 16, 2026 21:14
hyperpolymath
approved these changes
Nov 16, 2026
Merged
3 of 4 tasks
hyperpolymath
added a commit
that referenced
this pull request
Nov 17, 2026
… on React 18 and 19 types (#344) ## Change and reason Dependabot's React bump (#332, react 18.3.1 to 19.3.1, @types/react 19.3.0) fails `tsc && vite build` with: ``` src/views/TreeView.tsx(186,21): error TS2554: Expected 1 arguments, but got 0. src/views/TreeView.tsx(231,23): error TS2554: Expected 1 arguments, but got 0. ``` React 19's types make the `useRef` argument required. `useRef<number>()` in `TreeView.tsx` (two places: `saveTimer`, `scrollTimer`) becomes `useRef<number | undefined>(undefined)`, which typechecks on React 18 and 19 types and behaves the same at runtime. A search of `frontend/src` found no other argument-less `useRef`/`createRef`. Same forward-compatible preparation as #342 and #343. ## Validation Bun 1.4.4, `bun install --frozen-lockfile --ignore-scripts`, in `frontend/`: - Baseline (unchanged tree, React 18): `bun run build` passes, `bun run typecheck` passes, `bun test src` 90 pass / 0 fail. - After the change (React 18): build passes (`built in 34.45s`), typecheck passes, 90 pass / 0 fail. - React 19 in a scratch copy outside the repo (react and react-dom 19.3.1, @types/react 19.3.0, @types/react-dom 19.3.0), nothing committed: - Unfixed source (negative control): `tsc` reproduces exactly the two TS2554 errors above; tests 90 pass / 0 fail. - Fixed source: `bun run build` passes (`built in 20.22s`), tests 90 pass / 0 fail. Not run: Julia and R jobs (this change touches one frontend file); CI on this PR covers them. `scripts/lint-sonar-reliability.sh` and SonarCloud were not run locally. ## Scope One file, two lines. No `package.json` or lockfile change; the React bump itself stays in #332. ## Contribution checks - [x] I followed [CONTRIBUTING.md](../CONTRIBUTING.md). - [x] This branch starts at current main (6bb2ad2) and contains no merges from fork main. - [ ] CI has run and passes. - [x] Existing licensing, citation and acknowledgement text is unchanged. --- _Generated by [Claude Code](https://claude.ai/code/session_01J4QvDiW8qD4f2JDQJ4buGo)_ ## CI/gate The account ruleset "Branch-Floor" requires a status check named exactly `CI/gate`; this repository never emitted it. Commit 6ca65cc adds one job to `.github/workflows/ci.yml`: id `ci-status`, `name: CI/gate`, `needs` all seven other jobs (denominator 7), `if: always()`, `permissions: {}`, pure `run:` shell (no `uses:`, nothing new to pin). No trigger, path filter, existing job or check name was changed. The branch still starts at the tip of origin/main (6bb2ad2) with no merge commits; no rebase was needed. Rules, from the `if:` conditions in the file: - `gate` and `occupancy_gate` (detectors) must be `success`. - `test`, `standards`, `agda` are governed by `gate`: `success` when `gate` succeeded with `relevant == 'true'`, `skipped` only when `gate` succeeded with `relevant == 'false'`. - `occupancy`, `disagreement` are governed by `occupancy_gate` in the same way. - A skip while the detector failed, was cancelled, was skipped, or gave no usable output fails the gate. `failure`, `cancelled`, empty or unknown results exit 1. - A table of job, result, expected, verdict goes to the log and `$GITHUB_STEP_SUMMARY`. Local evidence (decision script extracted from the YAML, run with `NEEDS_JSON` set by hand; `jq`): - all success, both detectors relevant: exit 0 - agda failure: exit 1 - test cancelled: exit 1 - designed skip (both detectors success, relevant false, five jobs skipped): exit 0 - skips with `gate` failed: exit 1 - skips with `gate` skipped: exit 1 - detector says relevant but job skipped: exit 1 - unknown result `weird`: exit 1 - empty `needs`: exit 1 YAML parsed with Bun's YAML parser: the new job's name, needs and the unchanged `on:` block were read back correctly. NOT RUN: the repository's Julia test `test/unit/test_install_pins.jl` (no Julia here; by reading it, `CI/gate` has no `${{` and no matrix, so it should hold), `actionlint` (not installed). <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **CI** * Added a required status check that verifies relevance gates and governed job results, and reports a summary of the outcomes. * **Refactor** * No user-visible behavior changes. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude <noreply@anthropic.com>
|
auto-merge was automatically disabled
November 17, 2026 17:37
Pull request was closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Bumps react and @types/react. These dependencies needed to be updated together.
Updates
reactfrom 18.3.1 to 19.3.1Release notes
Sourced from react's releases.
... (truncated)
Changelog
Sourced from react's changelog.
... (truncated)
Commits
61aa00d[19.3.x][Flight] Improve transport protocol (#37845)2dc7da7[test] Bump Jest to 30.4 (#37382)4f93894docs: remove stale parentType param from validateChildKeys JSDoc (#36928)dbc3750Update required references to GitHub repo (#36752)900ae09[flow] Bump flow to v0.317.0 (#36701)fbb1370[flow] Bump flow to v0.307.1 (#36199)56922cf[react-native-renderer] Delete Paper (legacy) renderer (#36285)74568e8[Flight] TransportAggregateErrors.errors(#36156)e66ef64[tests] remove withoutStack from assertConsole helpers (#35498)db71391[Fiber] Instrument the lazy initializer thenable in all cases (#35521)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for react since your current version.
Updates
@types/reactfrom 18.3.31 to 19.3.0Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)