docs(backend): note M2MToken timestamps are in milliseconds#9122
Conversation
Clarify in the `M2MToken` JSDoc that `expiration`, `createdAt`, and `updatedAt` are Unix timestamps in milliseconds (not seconds). The constructor already converts JWT `exp`/`iat` claims via `* 1000`, so the values are milliseconds; only the doc comments were ambiguous. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: d709d0c The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 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.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Repository UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✅ Files skipped from review due to trivial changes (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughClarifies that timestamp fields in ChangesTimestamp unit documentation
Estimated code review effort: 1 (Trivial) | ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
Comment |
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@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: |
API Changes Report
Summary
No API Changes DetectedAll packages have stable APIs with no detected changes. Report generated by Break Check Last ran on |
…milliseconds Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Pushed one commit directly in d709d0c — extended the same clarification to the sibling machine-auth resources, which have the identical ambiguity:
Both verified against the backing service the same way as |
|
@wobsoriano I don't think @SarahSoutoul or I have permissions to merge in this repo. Can you mash the button for us or grant us permission?
|
Merged! I do not have powers to grant permissions 😅 |

Description
Clarify in the
M2MTokenJSDoc thatexpiration,createdAt, andupdatedAtare Unix timestamps in milliseconds (not seconds). The constructor already converts JWTexp/iatclaims via* 1000, so the values are milliseconds; only the doc comments were ambiguous.clerk-docsChecklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
Summary by CodeRabbit
Summary by CodeRabbit
expiration,createdAt,lastUsedAt,updatedAt) are Unix timestamps expressed in milliseconds.