Repository navigation
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d40928d614
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "dayjs": "1.11.23", | ||
| "dockerode": "^5.0.1", | ||
| "express": "5.2.1", | ||
| "express": "5.3.0", |
There was a problem hiding this comment.
Update authoritative dependency docs with these bumps
After this manifest update, agents and maintainers consulting the documented dependency baseline receive incorrect versions: GEMINI.md:42-43 still identifies Express 5.2 and Objection 3.1, while docs/wiki-intern/architektur/externe-abhaengigkeiten.md:13-17 still lists Express 5.2.1, Objection 3.1.5, and mysql2 3.24.5; that page also retains numerous old frontend and tooling versions through lines 69-96. Only the Vite marker in entwicklung/tests.md was synchronized, so update both authoritative inventories alongside the manifests to prevent future compatibility work from using a stale baseline.
AGENTS.md reference: AGENTS.md:L3-L9
Useful? React with 👍 / 👎.
| integrity sha512-zkd+e9S1AQHhmaBKye9zlFHWjOwVgqXl1q3ECYy8561K7qxR2cREf/STLskulBFd78k6AOFeA+ff1TtEzk9bAA== | ||
| dependencies: | ||
| nanoid "^3.3.18" | ||
| nanoid "^3.3.20" |
There was a problem hiding this comment.
Stop forcing NanoID below PostCSS's supported range
PostCSS 8.5.30 now declares nanoid ^3.3.20 here, but backend/package.json:69 still overrides the vitest/vite/postcss/nanoid path to 3.3.18, and the regenerated lockfile consequently retains nanoid@3.3.18. On a fresh backend install this selective override is outside the parent's supported range; Yarn Classic documents that such incompatibilities only produce a warning, so the frozen install and verification workflow can pass while the test/build stack runs an unsupported transitive version. Remove the obsolete security pin or raise it to a version satisfying ^3.3.20, and update the corresponding constraint test.
Useful? React with 👍 / 👎.
| "mysql2": "^3.24.5", | ||
| "objection": "3.1.5", | ||
| "mysql2": "^3.24.6", | ||
| "objection": "3.9.0", |
There was a problem hiding this comment.
Revert the untraceable Objection release
Every production backend install now loads objection@3.9.0, but this version is not traceable to the project's published source: the official npm package page and the upstream changelog still identify 3.1.5 as the latest release, while the first post-3.1 package visible to independent indexing was 3.3.0 published only three days earlier with zero downloads and a changed maintainer count. Tests can verify API behavior but cannot establish the provenance of a registry-only artifact that executes with database and filesystem access; keep 3.1.5 pinned until 3.9.0 has a verifiable upstream tag, changelog, and source diff.
Useful? React with 👍 / 👎.
Automated Dependency Updates
This PR updates direct frontend and backend dependencies to their latest published versions.
Frontend Updates
Backend Updates
Verification
THIRD-PARTY-NOTICES.mdafter all license scans succeeded.