feat: overlapping JWT keys, transactional boundaries, index audit, lo… - #1435
Conversation
…st-update prevention - JWT: support overlapping keys via JWT_SECRETS/JWT_CURRENT_KID, kid header, rotation with zero session loss, unknown kid rejected, single-secret backward compat, tests for sign/verify/rotation - Transactions: audit every multi-row write path, wrap in prisma.$transaction with timeout/maxWait/isolationLevel, move external RPC/webhooks outside, document in backend/docs/TRANSACTIONS.md, add rollback test - Indexes: audit every where/orderBy, add composite indexes ordered equality->range, migration adds concurrently, EXPLAIN before/after for top 5 queries, docs/INDEXES_AUDIT.md and INDEX_EXPLAIN.md - Concurrency: atomic increment/decrement for counters, version column on Goal/Streak/AnalyticsDaily, optimistic retry with bounded retries, 100 parallel increments test, documented in ARCHITECTURE.md
|
@Mikey-222 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
…ctions-indexes-concurrency
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 21431574 | Triggered | Generic Password | 187f263 | .github/workflows/pr-checks.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
|
Please resolve conflicts |
2 participants
Description
Closes #
Type of Change
Please mark the options that are relevant:
Changes Made
How to Test
Checklist
💻 Smart Contract Changes (if applicable)
cargo fmt -- --checkpasses successfully.cargo clippy -- -D warningsruns without any warnings.cargo test.🎨 Frontend Changes (if applicable)
npm run typecheckornpx tsc --noEmit).npm run lintshows no linting errors.npm run build.⚙️ General
console.logor debug code remains in production files.mainbranch.Screenshots / Demos (if applicable)