feat(shared): Add oiat field to JwtHeader type#8107
Conversation
Session Minter uses oiat (original_issued_at) in the JWT header to track when token claims were last assembled from the DB. Edge re-mints copy this value forward, so consumers can determine claim freshness regardless of how many times the token was re-signed. Marked @internal so developers don't depend on this field.
🦋 Changeset detectedLatest commit: ee6914d The changes in this PR will be included in the next version bump. This PR includes changesets to release 21 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis pull request adds a changeset entry for the 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Resolve tokenCache.ts conflict by adopting main's orphan guard (cache.get(key) !== value short-circuit from #8098); drop the PR's redundant compare-and-swap. Monotonic enforcement remains at the broadcast handler, cookie write path, and Session resource where user-visible state lives. Drop stale changesets that were superseded by merged work: - session-minter-oiat-type.md (oiat field shipped via #8107) - session-minter-sdk-params.md (previous-token + force_origin shipped via #8105 + #8106 + #8107)
Resolve tokenCache.ts conflict by adopting main's orphan guard (cache.get(key) !== value short-circuit from #8098); drop the PR's redundant compare-and-swap. Monotonic enforcement remains at the broadcast handler, cookie write path, and Session resource where user-visible state lives. Drop stale changesets that were superseded by merged work: - session-minter-oiat-type.md (oiat field shipped via #8107) - session-minter-sdk-params.md (previous-token + force_origin shipped via #8105 + #8106 + #8107)
Why
Session Minter uses
oiat(original_issued_at) in the JWT header to track when token claims were last assembled from the DB. Edge re-mints copy this value forward, so consumers can determine claim freshness regardless of how many times the token was re-signed at the edge.What
Add
oiat?: numberto theJwtHeaderinterface injwtv2.ts. Marked@internal.Test plan
Summary by CodeRabbit