Repository navigation
chore(identity): clarify the profile ETag's scope after #1425 - #1433
Merged
Merged
Conversation
The tag hashes only the PUT /profile fields, so note it must never back a 304, and fix the dashboard comment that still credited the concurrency stamp. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Comment-only follow-ups from the #1425 review:
GetUserProfileEndpoint: the ETag hashes only the fieldsPUT /profilewrites, so it's a write precondition and must never back a conditionalGET/304.clients/dashboard/src/pages/settings/profile.tsx: the avatar comment still said Identity rotates the concurrency stamp; it's now the hashed avatar URL that moves the tag.No behaviour change, no docs change.
🤖 Generated with Claude Code