Repository navigation
Patch production dependencies and verify them in CI - #57
Merged
Merged
Conversation
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.
The production dependency audit reported one critical and seven high-severity findings. This updates Next.js and its ESLint configuration to 16.4.6, React to the patched 19.2 release, Zod and source-map-js to patched versions, and the transitive merger in Prisma configuration. The project keeps its existing Prisma 6 database client and migration strategy.
CI now checks high-severity production advisories. The runbook records the Cloud Monitoring ingestion policy, database backups and safe default for the manual migration job. The README distinguishes submission keys from gateway keys.
Local production audit reports zero vulnerabilities. Prisma generation, lint, 176 unit tests and the production build passed.