Skip to content

Check the idempotency fingerprint before decrypting stored responses - #946

Merged
schustmi merged 1 commit into
developfrom
bugfix/idempotency-decrypt-order
Sep 1, 2026
Merged

Check the idempotency fingerprint before decrypting stored responses#946
schustmi merged 1 commit into
developfrom
bugfix/idempotency-decrypt-order

Conversation

@schustmi

@schustmi schustmi commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Fixes #931

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@schustmi
schustmi requested a review from strickvl September 1, 2026 12:55
@schustmi
schustmi force-pushed the bugfix/idempotency-decrypt-order branch from 0064e27 to eca7ae4 Compare September 1, 2026 13:54
@schustmi
schustmi merged commit 17ce9b5 into develop Sep 1, 2026
31 checks passed
@schustmi
schustmi deleted the bugfix/idempotency-decrypt-order branch September 1, 2026 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reusing an Idempotency-Key across routes 500s on POST /api/v1/api-keys (decrypt runs before the fingerprint check)

2 participants