feat(api-keys): add api key expiration - #222
Merged
mijinummi merged 2 commits intoAug 20, 2026
Merged
Conversation
mijinummi
merged commit Aug 20, 2026
0b0cae0
into
MD-Creative-Production:main
10 of 13 checks passed
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
Implements #108 by completing the API key entity with expiration support
while preserving the existing ownership and revocation relationships.
Changes
expiresAtfield toApiKey.expiresAtfor efficient expiration queries.User -> ApiKeyownership relationship.API Key Entity
The
ApiKeyentity now supports:userId.Database
Generated Prisma migration:
add_api_key_expirationValidation
npx prisma validatenpx prisma formatnpx prisma generatenpx prisma migrate statusnpm run format:checknpm run lintnpm run typechecknpm testnpm run buildCloses #108