Repository navigation
test(gateway-keys): pin the clock so CI survives the key expiry date - #375
Merged
Merged
Conversation
…XPIRES Minting correctly refuses once the event expiry (2026-11-16T01:00Z) has passed, so 12 tests that mint on the real clock went red on develop. _key_duration now reads _utc_now() (a seam); the test fixture pins it to before the expiry. No behaviour change. Co-Authored-By: Claude Fable 5.2 <[email protected]>
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.
CI on
developwent red on Nov 16:GATEWAY_KEY_EXPIRES(2026-11-16T01:00Z) passed, and_key_duration()correctly refuses to mint a key that is already expired, so the 12 tests that mint on the real clock fail._key_durationreads a new_utc_now()seam (no behaviour change).api/teams/tests: 218 passed (was 12 failed, 205 passed).🤖 Generated with Claude Code