Repository navigation
Repair receipt publication preflight and dependency security checks - #5
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.
Receipt publication could exceed the transaction gas ceiling, and staging tooling required the full asset scope. Add capped gas estimation, wallet preflight, and an explicit staging-only partial-scope opt-in while preserving one receipt per forecast.
Restore the CI security audit with Next.js 16.3.8, a patched gRPC 1.14.5 override for Firebase's older pinned dependency, and compatible brace-expansion, fast-uri and undici updates.
Validation: 177 deterministic tests passed across 27 suites; TypeScript and production build passed against a fresh npm ci; npm audit reports zero vulnerabilities. No attestations or live ledger writes were executed.