Repository navigation
test(auth): always alter the passkey signature fixture - #459
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.
The negative passkey-cookie test checked the signature’s last character while replacing its first. With a random development signing secret it could therefore leave the signature unchanged and intermittently fail otherwise unrelated CI runs.
Choose the replacement using the first character that is actually replaced. Documents the fixture rule. Formatting and comment checks passed; tests run in CI per maintainer instruction. No production behavior changes.
Fixes the failure observed in PR #452’s PostgreSQL-backed test job.