security: surface next-major Prisma remediation evidence - #3258
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
smkc | 154d807 | Sep 10 2026, 08:41 PM |
azumag
commented
Sep 10, 2026
azumag
left a comment
Owner
Author
There was a problem hiding this comment.
コード・設計・テストを確認しました。blocking finding はありません。next-major probe は既存の canonical registry / stable-only / dependency-edge 判定を再利用し、current ^6.19.3 から次 major を導出する場合も caret selector に限定して fail-closed です。workflow 側も continue-on-error の advisory evidence に留め、既存の compatible_upstream_gate に next-major state を混ぜていないため、Prisma 6→7 の重大な仕様判断を自動化していません。新規 script / workflow contract の回帰テストと runbook も整合しています。初回CIの changed-file formatting 失敗は同PRで修正済みで、最新HEADでは Prisma/D1 parity・lint・format・unit tests・security audit が成功しています。Cloudflare/review workflow の最終完了だけ継続確認します。
4 tasks
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.
Summary
Advance #3114 without applying a breaking Prisma upgrade.
security-audit-next-major.jsprobe that derives the next major only from the current caret Prisma selector and reuses the existing canonical-registry / stable-only / dependency-edge checks@prisma/config→deepmerge-tsevidence and an observation timestamp in the manual Security audit review summarycontinue-on-error) so the existing current-range fail-closed gate is unchangedWhy
Prisma upstream PR prisma/orm#30189 was merged to the
v7branch on 2026-09-01 and bumpsdeepmerge-tsto a patched 8.x release. JSMKC currently uses Prisma^6.19.3, so the existing compatible-range probe correctly cannot see that remediation. This change records that a next-major remediation path exists without silently treating Prisma 6 → 7 as a safe automatic update.Safety
No dependency versions, lockfile contents, production behavior, #3114 exception scope/deadline, audit severity, or consumer-side overrides are changed. A Prisma major upgrade still requires a separate explicit migration PR and full compatibility validation.