clerk · wobsoriano · Aug 12, 2025 · Aug 9, 2025 · Aug 9, 2025 · Aug 9, 2025
diff --git a/.changeset/eighty-plums-listen.md b/.changeset/eighty-plums-listen.md
@@ -0,0 +1,2 @@
+---
+---
diff --git a/integration/presets/longRunningApps.ts b/integration/presets/longRunningApps.ts
@@ -31,7 +31,6 @@ export const createLongRunningApps = () => {
     { id: 'next.appRouter.withSignInOrUpFlow', config: next.appRouter, env: envs.withSignInOrUpFlow },
     { id: 'next.appRouter.withSignInOrUpEmailLinksFlow', config: next.appRouter, env: envs.withSignInOrUpEmailLinksFlow },
     { id: 'next.appRouter.withSessionTasks', config: next.appRouter, env: envs.withSessionTasks },
-    { id: 'next.appRouter.withAPIKeys', config: next.appRouter, env: envs.withAPIKeys },
     { id: 'next.appRouter.withLegalConsent', config: next.appRouter, env: envs.withLegalConsent },
 
     /**
@@ -49,9 +48,9 @@ export const createLongRunningApps = () => {
 
     /**
      * Machine auth apps
-     * TODO(rob): Group other machine auth apps together (api keys, m2m tokens, etc)
      */
     { id: 'withMachine.express.vite', config: express.vite, env: envs.withAPIKeys },
+    { id: 'withMachine.next.appRouter', config: next.appRouter, env: envs.withAPIKeys },
 
     /**
      * Vite apps - basic flows

diff --git a/integration/tests/machine-auth/api-keys.test.ts b/integration/tests/machine-auth/api-keys.test.ts
@@ -7,7 +7,7 @@ import { appConfigs } from '../../presets';
 import type { FakeAPIKey, FakeUser } from '../../testUtils';
 import { createTestUtils } from '../../testUtils';
 
-test.describe('Next.js API key auth within clerkMiddleware() @nextjs', () => {
+test.describe('Next.js API key auth within clerkMiddleware() @machine', () => {
-test.describe('Next.js API key auth within clerkMiddleware() @machine', () => {
+test.describe('Next.js API key auth within routes @nextjs @machine', () => {
-test.describe('Next.js API key auth within clerkMiddleware() @machine', () => {
+test.describe('Next.js API key auth within routes @nextjs @machine', () => {
   test.describe.configure({ mode: 'parallel' });
   let app: Application;
   let fakeUser: FakeUser;

diff --git a/integration/tests/machine-auth/component.test.ts b/integration/tests/machine-auth/component.test.ts
@@ -4,7 +4,10 @@ import { appConfigs } from '../../presets';
 import type { FakeOrganization, FakeUser } from '../../testUtils';
 import { createTestUtils, testAgainstRunningApps } from '../../testUtils';
 
-testAgainstRunningApps({ withEnv: [appConfigs.envs.withAPIKeys] })('api keys @generic', ({ app }) => {
+testAgainstRunningApps({
+  withEnv: [appConfigs.envs.withAPIKeys],
+  withPattern: ['withMachine.next.appRouter'],
+})('api keys component @machine', ({ app }) => {
   test.describe.configure({ mode: 'serial' });
 
   let fakeAdmin: FakeUser;
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		---
		---
Comment on lines +1 to +2 Copy link Contributor coderabbitai bot Aug 12, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. 💡 Verification agent 🧩 Analysis chain Empty Changeset is likely non-actionable and may confuse/impact the release workflow This file only contains YAML front matter delimiters with no package bumps or summary. Depending on your Changesets setup, this can either be ignored or cause CI confusion. For test-only/grouping changes, prefer either removing the changeset entirely or adding a proper bump if a release is intended. If no release is intended: remove this file. If a release is intended: specify the packages and bump type, plus a short summary. Run the following to inspect repo configs and references to the Changesets workflow to ensure an empty changeset is acceptable here: 🏁 Script executed: #!/bin/bash set -euo pipefail echo "List changeset files:" fd -a '^.+\.md$' .changeset \|\| true echo -e "\nShow Changesets config (if present):" if [ -f ".changeset/config.json" ]; then cat .changeset/config.json else echo "No .changeset/config.json found" fi echo -e "\nLook for GH Actions using changesets:" fd -a ".github/workflows" \| xargs -I{} rg -n "changeset\|Changesets" {} \|\| true echo -e "\nSearch for Danger/CI rules that mandate changesets:" rg -n "changeset\|Changesets\|require-changeset\|no-changeset" -S . \|\| true echo -e "\nIf CI requires a changeset for every PR, confirm if an 'empty' changeset is allowed or if a special label should be used instead." Length of output: 14405 Clarify Intent for This Empty Changeset This file is an intentionally empty changeset (just the `---` front-matter) created by `pnpm changeset:empty`. Per our CONTRIBUTING guide, empty changesets are supported as an “escape hatch” for internal refactors or test-only PRs and will not generate any changelog entries. • If you intended not to produce a release or changelog entry, no further action is needed. • If you do want to publish changes, update this file’s front-matter to list the affected package(s), bump type (patch/minor/major), and add a brief summary. 🤖 Prompt for AI Agents In .changeset/eighty-plums-listen.md around lines 1 to 2, the changeset contains only empty front-matter (---) so you must either leave it as-is if this PR is intentionally test/internal and shouldn't produce a release, or update the front-matter to declare the affected package(s), bump type, and a short summary; to fix it, replace the front-matter with a YAML block listing the package names and their release types (patch/minor/major) and add a one-line summary describing the change so the changeset will generate a changelog/release for those packages. Comment on lines +1 to +2 Copy link Contributor coderabbitai bot Aug 12, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. ⚠️ Potential issue Invalid/empty Changeset frontmatter will break the Changesets pipeline The file only contains an empty frontmatter block (`---` … `---`) without any package release entries or summary. This typically causes the Changesets step to fail parsing. Action: Either remove the changeset if your repo allows test-only PRs without a changeset, or Populate it with valid entries (use `none` for all relevant packages if you do not intend to publish), and add a short summary line. Example template (replace PACKAGE_NAME with actual workspace package names): --- 'PACKAGE_NAME': none --- chore(repo): Group related machine auth tests I can help enumerate workspace package names to fill this properly if needed. 🤖 Prompt for AI Agents .changeset/eighty-plums-listen.md lines 1-2: the changeset contains only an empty frontmatter block which breaks the Changesets pipeline; either delete the file if this PR shouldn't include a changeset, or replace the empty frontmatter with valid frontmatter listing workspace package names and release types (use 'none' for packages you don't intend to publish) and add a short summary body line beneath the frontmatter (e.g. three lines: frontmatter mapping, closing dashes, and a one-line summary).