Repository navigation
Conversation
Bumps [jest](https://github.com/jestjs/jest/tree/HEAD/packages/jest) from 30.4.2 to 30.5.2. - [Release notes](https://github.com/jestjs/jest/releases) - [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md) - [Commits](https://github.com/jestjs/jest/commits/v30.5.2/packages/jest) --- updated-dependencies: - dependency-name: jest dependency-version: 30.5.2 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumping jest alone left jest-environment-jsdom at 30.4.1, so the shared Jest packages stayed on 30.4.x and jest 30.5.2 got its own nested copies: 151 extra packages and two versions of Jest's core in the tree. Bump jest-environment-jsdom to 30.5.2 too and re-resolve the lockfile from uat's, so each Jest package has one version (914 packages, uat has 920). Group jest, jest-*, @jest/* and @types/jest in Dependabot so they are proposed together from now on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-30.5.2 Bump jest and jest-environment-jsdom to 30.5.2 together
_app.tsx created a new QueryClient on every render, so the cache was empty after each navigation and the 1 MB+ drugs.json was downloaded again. Keep one client in useState, and drop the second QueryClient and LocalizationProvider that Factsheets.tsx wrapped itself in. The factsheets table and the factsheet pages each had their own query under the same "table-data" key but with different data shapes, which would clash in a shared cache. Both now use one useDrugs() hook (src/utils/drugs.ts) with a 30 minute staleTime; a failed download now throws. Removing the table's rowCount also fixes the pager showing "1-10 of 555" after filtering (WEB-029). The tracker gains WEB-027 to WEB-030 for the issues found while deploying and testing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep one QueryClient and share the drugs query (WEB-007, WEB-029)
The ban-appeal login failed after sign-in: the browser asked Keycloak for a code as the "website" client, but TripBot redeems it as the ban-appeals client, and Keycloak binds a code to the client that requested it. Next.js writes NEXT_PUBLIC_* values into the browser bundle during next build. The Dockerfile never declared them, so the build saw none and the bundle always fell back to "website". Declare NEXT_PUBLIC_DNS_DOMAIN, NEXT_PUBLIC_KEYCLOAK_URL and NEXT_PUBLIC_KEYCLOAK_CLIENT_ID as ARG/ENV in the build stage so compose build.args reach it. keycloak.ts said its config was read "at runtime instead of build time", which is wrong for client code; the comment now says how it works. The "website" fallback is gone: a missing client ID throws outside production, and in production it is logged and Keycloak rejects the request before the user signs in, instead of TripBot failing afterwards. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bump every outdated direct dependency to its latest release, including apexcharts 5 -> 8, react 19.3, eslint 10.14, typescript-eslint 8.72 and testing-library, and refresh the lockfile. This picks up Dependabot's eslint (#263) and user-event (#262) bumps and clears the two high advisories (zod, brace-expansion). apexcharts 6-8 moved some chart types and features into separate imports, but rangeBar, the only type we use, stays in the default bundle. Both factsheet charts render on a production build with no console warnings. Drop the @babel/helper-plugin-utils 7.26.5 override: tests and coverage pass on 7.29.7 with @babel/core 7.29.7. TypeScript stays on 6 because typescript-eslint supports <6.1.0. The remaining moderate and low advisories are under eslint and jest and need upstream releases; see WEB-026. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pass the Keycloak client ID to next build (WEB-031)
Update dependencies to their latest versions (WEB-026)
LunaUrsa
approved these changes
Nov 8, 2026
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.
Auto-opened by the OpenUatToMainPR workflow after a push to
uat. Merge to release these changes to production.