docs(backend): note M2MToken timestamps are in milliseconds

[SarahSoutoul]

Description

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.

• Linear ticket
• Sibling PR on clerk-docs

Checklist

• pnpm test runs as expected.
• pnpm build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

Summary by CodeRabbit

• Documentation
  • Clarified that machine-to-machine token expiration, createdAt, and updatedAt timestamps are Unix timestamps expressed in milliseconds.
  • Updated the release notes to reflect this documentation clarification.

[changeset-bot]

🦋 Changeset detected

Latest commit: ac6d46e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 10 packages

Name	Type
@clerk/backend	Patch
@clerk/astro	Patch
@clerk/express	Patch
@clerk/fastify	Patch
@clerk/hono	Patch
@clerk/nextjs	Patch
@clerk/nuxt	Patch
@clerk/react-router	Patch
@clerk/tanstack-react-start	Patch
@clerk/testing	Patch

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jul 10, 2026 10:22am
swingset	Ready	Preview, Comment	Jul 10, 2026 10:22am

[coderabbitai]

📝 Walkthrough

Walkthrough

Clarifies that M2MToken timestamp fields use Unix timestamps in milliseconds and adds a patch changeset for @clerk/backend.

Changes

M2M token timestamp documentation

Layer / File(s)	Summary
Clarify timestamp units packages/backend/src/api/resources/M2MToken.ts, .changeset/m2m-token-timestamp-units.md	Updates constructor JSDoc and the patch changeset to specify millisecond-based Unix timestamps for M2M token fields.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Poem

I’m a rabbit with timestamps bright,
Milliseconds now hop into sight.
The docs wear a clearer tune,
With a patch release arriving soon.
Hop, hop—precision blooms!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: clarifying that M2MToken timestamps are in milliseconds.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@9122

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@9122

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@9122

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@9122

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9122

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9122

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9122

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@9122

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@9122

@clerk/express

npm i https://pkg.pr.new/@clerk/express@9122

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@9122

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@9122

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@9122

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@9122

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@9122

@clerk/react

npm i https://pkg.pr.new/@clerk/react@9122

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@9122

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@9122

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@9122

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@9122

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@9122

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@9122

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@9122

commit: ac6d46e

[github-actions]

API Changes Report

Generated by Break Check on 2026-07-10T10:24:31.139Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

No API Changes Detected

All packages have stable APIs with no detected changes.

---

Report generated by Break Check

_{Last ran on ac6d46e.}

[wobsoriano]

thanks!