fix(env-pull): default to .env.local on Next.js projects by rafa-thayto · Pull Request #204 · clerk/cli

rafa-thayto · 2026-04-22T15:16:22Z

Summary

clerk env pull on a Next.js project with no existing env file now creates .env.local instead of .env, matching the framework's convention for per-machine secrets (and Vercel's vercel env pull behavior)
Projects that already have Clerk keys in .env keep writing there — the hasClerkKeys backwards-compat branch in resolveTargetFile is unchanged
Fixes the misleading comment in framework.ts about which frameworks gitignore .env

Test plan

bun run test — all 78 files pass
bun run format, bun run lint, bun run typecheck — clean
Manual: run clerk env pull in a fresh create-next-app project, confirm .env.local is created with NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY
Manual: run clerk env pull in a Next.js project that already has Clerk keys in .env, confirm keys are still written to .env (no new .env.local)

Running `clerk env pull` on a Next.js project with no existing env file was creating `.env`, which violates the framework convention where `.env.local` is the home for per-machine secrets. Flip the Next.js entry in FRAMEWORK_MAP to `.env.local`. The backwards-compat branch in `resolveTargetFile` still detects existing Clerk keys in `.env` and keeps writing there, so projects that ran earlier `env pull` versions are unaffected.

changeset-bot · 2026-04-22T15:16:38Z

🦋 Changeset detected

Latest commit: ff8f88d

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

This PR includes changesets to release 1 package

Name	Type
clerk	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

coderabbitai · 2026-04-22T15:19:08Z

📝 Walkthrough

Walkthrough

This change modifies the behavior of the clerk env pull command for Next.js projects. When no environment file exists, the command now defaults to writing pulled environment variables to .env.local instead of .env, aligning with Next.js's local secrets convention. If .env already contains existing keys, the command continues writing to .env. The change includes updates to the framework configuration in FRAMEWORK_MAP, corresponding test assertions across unit and integration tests, and Changesets metadata documentation.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating `clerk env pull` to default to `.env.local` for Next.js projects, which is clearly reflected across all modified files and test updates.
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	The pull request description clearly explains the changes: updating `clerk env pull` behavior for Next.js projects to default to `.env.local`, maintaining backward compatibility, and fixing documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

rafa-thayto · 2026-04-22T15:16:22Z

Summary

clerk env pull on a Next.js project with no existing env file now creates .env.local instead of .env, matching the framework's convention for per-machine secrets (and Vercel's vercel env pull behavior)
Projects that already have Clerk keys in .env keep writing there — the hasClerkKeys backwards-compat branch in resolveTargetFile is unchanged
Fixes the misleading comment in framework.ts about which frameworks gitignore .env

Test plan

bun run test — all 78 files pass
bun run format, bun run lint, bun run typecheck — clean
Manual: run clerk env pull in a fresh create-next-app project, confirm .env.local is created with NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY
Manual: run clerk env pull in a Next.js project that already has Clerk keys in .env, confirm keys are still written to .env (no new .env.local)

Running `clerk env pull` on a Next.js project with no existing env file was creating `.env`, which violates the framework convention where `.env.local` is the home for per-machine secrets. Flip the Next.js entry in FRAMEWORK_MAP to `.env.local`. The backwards-compat branch in `resolveTargetFile` still detects existing Clerk keys in `.env` and keeps writing there, so projects that ran earlier `env pull` versions are unaffected.

changeset-bot · 2026-04-22T15:16:38Z

🦋 Changeset detected

Latest commit: ff8f88d

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

This PR includes changesets to release 1 package

Name	Type
clerk	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

coderabbitai · 2026-04-22T15:19:08Z

📝 Walkthrough

Walkthrough

This change modifies the behavior of the clerk env pull command for Next.js projects. When no environment file exists, the command now defaults to writing pulled environment variables to .env.local instead of .env, aligning with Next.js's local secrets convention. If .env already contains existing keys, the command continues writing to .env. The change includes updates to the framework configuration in FRAMEWORK_MAP, corresponding test assertions across unit and integration tests, and Changesets metadata documentation.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating `clerk env pull` to default to `.env.local` for Next.js projects, which is clearly reflected across all modified files and test updates.
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	The pull request description clearly explains the changes: updating `clerk env pull` behavior for Next.js projects to default to `.env.local`, maintaining backward compatibility, and fixing documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

rafa-thayto · 2026-04-22T15:16:22Z

Summary

clerk env pull on a Next.js project with no existing env file now creates .env.local instead of .env, matching the framework's convention for per-machine secrets (and Vercel's vercel env pull behavior)
Projects that already have Clerk keys in .env keep writing there — the hasClerkKeys backwards-compat branch in resolveTargetFile is unchanged
Fixes the misleading comment in framework.ts about which frameworks gitignore .env

Test plan

bun run test — all 78 files pass
bun run format, bun run lint, bun run typecheck — clean
Manual: run clerk env pull in a fresh create-next-app project, confirm .env.local is created with NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY
Manual: run clerk env pull in a Next.js project that already has Clerk keys in .env, confirm keys are still written to .env (no new .env.local)

Running `clerk env pull` on a Next.js project with no existing env file was creating `.env`, which violates the framework convention where `.env.local` is the home for per-machine secrets. Flip the Next.js entry in FRAMEWORK_MAP to `.env.local`. The backwards-compat branch in `resolveTargetFile` still detects existing Clerk keys in `.env` and keeps writing there, so projects that ran earlier `env pull` versions are unaffected.

changeset-bot · 2026-04-22T15:16:38Z

🦋 Changeset detected

Latest commit: ff8f88d

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

This PR includes changesets to release 1 package

Name	Type
clerk	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

coderabbitai · 2026-04-22T15:19:08Z

📝 Walkthrough

Walkthrough

This change modifies the behavior of the clerk env pull command for Next.js projects. When no environment file exists, the command now defaults to writing pulled environment variables to .env.local instead of .env, aligning with Next.js's local secrets convention. If .env already contains existing keys, the command continues writing to .env. The change includes updates to the framework configuration in FRAMEWORK_MAP, corresponding test assertions across unit and integration tests, and Changesets metadata documentation.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating `clerk env pull` to default to `.env.local` for Next.js projects, which is clearly reflected across all modified files and test updates.
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	The pull request description clearly explains the changes: updating `clerk env pull` behavior for Next.js projects to default to `.env.local`, maintaining backward compatibility, and fixing documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

rafa-thayto · 2026-04-22T15:16:22Z

Summary

clerk env pull on a Next.js project with no existing env file now creates .env.local instead of .env, matching the framework's convention for per-machine secrets (and Vercel's vercel env pull behavior)
Projects that already have Clerk keys in .env keep writing there — the hasClerkKeys backwards-compat branch in resolveTargetFile is unchanged
Fixes the misleading comment in framework.ts about which frameworks gitignore .env

Test plan

bun run test — all 78 files pass
bun run format, bun run lint, bun run typecheck — clean
Manual: run clerk env pull in a fresh create-next-app project, confirm .env.local is created with NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY
Manual: run clerk env pull in a Next.js project that already has Clerk keys in .env, confirm keys are still written to .env (no new .env.local)

Running `clerk env pull` on a Next.js project with no existing env file was creating `.env`, which violates the framework convention where `.env.local` is the home for per-machine secrets. Flip the Next.js entry in FRAMEWORK_MAP to `.env.local`. The backwards-compat branch in `resolveTargetFile` still detects existing Clerk keys in `.env` and keeps writing there, so projects that ran earlier `env pull` versions are unaffected.

changeset-bot · 2026-04-22T15:16:38Z

🦋 Changeset detected

Latest commit: ff8f88d

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

This PR includes changesets to release 1 package

Name	Type
clerk	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

coderabbitai · 2026-04-22T15:19:08Z

📝 Walkthrough

Walkthrough

This change modifies the behavior of the clerk env pull command for Next.js projects. When no environment file exists, the command now defaults to writing pulled environment variables to .env.local instead of .env, aligning with Next.js's local secrets convention. If .env already contains existing keys, the command continues writing to .env. The change includes updates to the framework configuration in FRAMEWORK_MAP, corresponding test assertions across unit and integration tests, and Changesets metadata documentation.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating `clerk env pull` to default to `.env.local` for Next.js projects, which is clearly reflected across all modified files and test updates.
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	The pull request description clearly explains the changes: updating `clerk env pull` behavior for Next.js projects to default to `.env.local`, maintaining backward compatibility, and fixing documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

rafa-thayto · 2026-04-22T15:16:22Z

Summary

clerk env pull on a Next.js project with no existing env file now creates .env.local instead of .env, matching the framework's convention for per-machine secrets (and Vercel's vercel env pull behavior)
Projects that already have Clerk keys in .env keep writing there — the hasClerkKeys backwards-compat branch in resolveTargetFile is unchanged
Fixes the misleading comment in framework.ts about which frameworks gitignore .env

Test plan

bun run test — all 78 files pass
bun run format, bun run lint, bun run typecheck — clean
Manual: run clerk env pull in a fresh create-next-app project, confirm .env.local is created with NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY
Manual: run clerk env pull in a Next.js project that already has Clerk keys in .env, confirm keys are still written to .env (no new .env.local)

Running `clerk env pull` on a Next.js project with no existing env file was creating `.env`, which violates the framework convention where `.env.local` is the home for per-machine secrets. Flip the Next.js entry in FRAMEWORK_MAP to `.env.local`. The backwards-compat branch in `resolveTargetFile` still detects existing Clerk keys in `.env` and keeps writing there, so projects that ran earlier `env pull` versions are unaffected.

changeset-bot · 2026-04-22T15:16:38Z

🦋 Changeset detected

Latest commit: ff8f88d

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

This PR includes changesets to release 1 package

Name	Type
clerk	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

coderabbitai · 2026-04-22T15:19:08Z

📝 Walkthrough

Walkthrough

This change modifies the behavior of the clerk env pull command for Next.js projects. When no environment file exists, the command now defaults to writing pulled environment variables to .env.local instead of .env, aligning with Next.js's local secrets convention. If .env already contains existing keys, the command continues writing to .env. The change includes updates to the framework configuration in FRAMEWORK_MAP, corresponding test assertions across unit and integration tests, and Changesets metadata documentation.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating `clerk env pull` to default to `.env.local` for Next.js projects, which is clearly reflected across all modified files and test updates.
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	The pull request description clearly explains the changes: updating `clerk env pull` behavior for Next.js projects to default to `.env.local`, maintaining backward compatibility, and fixing documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

rafa-thayto · 2026-04-22T15:16:22Z

Summary

clerk env pull on a Next.js project with no existing env file now creates .env.local instead of .env, matching the framework's convention for per-machine secrets (and Vercel's vercel env pull behavior)
Projects that already have Clerk keys in .env keep writing there — the hasClerkKeys backwards-compat branch in resolveTargetFile is unchanged
Fixes the misleading comment in framework.ts about which frameworks gitignore .env

Test plan

bun run test — all 78 files pass
bun run format, bun run lint, bun run typecheck — clean
Manual: run clerk env pull in a fresh create-next-app project, confirm .env.local is created with NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY
Manual: run clerk env pull in a Next.js project that already has Clerk keys in .env, confirm keys are still written to .env (no new .env.local)

Running `clerk env pull` on a Next.js project with no existing env file was creating `.env`, which violates the framework convention where `.env.local` is the home for per-machine secrets. Flip the Next.js entry in FRAMEWORK_MAP to `.env.local`. The backwards-compat branch in `resolveTargetFile` still detects existing Clerk keys in `.env` and keeps writing there, so projects that ran earlier `env pull` versions are unaffected.

changeset-bot · 2026-04-22T15:16:38Z

🦋 Changeset detected

Latest commit: ff8f88d

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

This PR includes changesets to release 1 package

Name	Type
clerk	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

coderabbitai · 2026-04-22T15:19:08Z

📝 Walkthrough

Walkthrough

This change modifies the behavior of the clerk env pull command for Next.js projects. When no environment file exists, the command now defaults to writing pulled environment variables to .env.local instead of .env, aligning with Next.js's local secrets convention. If .env already contains existing keys, the command continues writing to .env. The change includes updates to the framework configuration in FRAMEWORK_MAP, corresponding test assertions across unit and integration tests, and Changesets metadata documentation.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating `clerk env pull` to default to `.env.local` for Next.js projects, which is clearly reflected across all modified files and test updates.
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	The pull request description clearly explains the changes: updating `clerk env pull` behavior for Next.js projects to default to `.env.local`, maintaining backward compatibility, and fixing documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

rafa-thayto · 2026-04-22T15:16:22Z

Summary

clerk env pull on a Next.js project with no existing env file now creates .env.local instead of .env, matching the framework's convention for per-machine secrets (and Vercel's vercel env pull behavior)
Projects that already have Clerk keys in .env keep writing there — the hasClerkKeys backwards-compat branch in resolveTargetFile is unchanged
Fixes the misleading comment in framework.ts about which frameworks gitignore .env

Test plan

bun run test — all 78 files pass
bun run format, bun run lint, bun run typecheck — clean
Manual: run clerk env pull in a fresh create-next-app project, confirm .env.local is created with NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY
Manual: run clerk env pull in a Next.js project that already has Clerk keys in .env, confirm keys are still written to .env (no new .env.local)

Running `clerk env pull` on a Next.js project with no existing env file was creating `.env`, which violates the framework convention where `.env.local` is the home for per-machine secrets. Flip the Next.js entry in FRAMEWORK_MAP to `.env.local`. The backwards-compat branch in `resolveTargetFile` still detects existing Clerk keys in `.env` and keeps writing there, so projects that ran earlier `env pull` versions are unaffected.

changeset-bot · 2026-04-22T15:16:38Z

🦋 Changeset detected

Latest commit: ff8f88d

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

This PR includes changesets to release 1 package

Name	Type
clerk	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

coderabbitai · 2026-04-22T15:19:08Z

📝 Walkthrough

Walkthrough

This change modifies the behavior of the clerk env pull command for Next.js projects. When no environment file exists, the command now defaults to writing pulled environment variables to .env.local instead of .env, aligning with Next.js's local secrets convention. If .env already contains existing keys, the command continues writing to .env. The change includes updates to the framework configuration in FRAMEWORK_MAP, corresponding test assertions across unit and integration tests, and Changesets metadata documentation.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating `clerk env pull` to default to `.env.local` for Next.js projects, which is clearly reflected across all modified files and test updates.
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	The pull request description clearly explains the changes: updating `clerk env pull` behavior for Next.js projects to default to `.env.local`, maintaining backward compatibility, and fixing documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

rafa-thayto · 2026-04-22T15:16:22Z

Summary

clerk env pull on a Next.js project with no existing env file now creates .env.local instead of .env, matching the framework's convention for per-machine secrets (and Vercel's vercel env pull behavior)
Projects that already have Clerk keys in .env keep writing there — the hasClerkKeys backwards-compat branch in resolveTargetFile is unchanged
Fixes the misleading comment in framework.ts about which frameworks gitignore .env

Test plan

bun run test — all 78 files pass
bun run format, bun run lint, bun run typecheck — clean
Manual: run clerk env pull in a fresh create-next-app project, confirm .env.local is created with NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY
Manual: run clerk env pull in a Next.js project that already has Clerk keys in .env, confirm keys are still written to .env (no new .env.local)

Running `clerk env pull` on a Next.js project with no existing env file was creating `.env`, which violates the framework convention where `.env.local` is the home for per-machine secrets. Flip the Next.js entry in FRAMEWORK_MAP to `.env.local`. The backwards-compat branch in `resolveTargetFile` still detects existing Clerk keys in `.env` and keeps writing there, so projects that ran earlier `env pull` versions are unaffected.

changeset-bot · 2026-04-22T15:16:38Z

🦋 Changeset detected

Latest commit: ff8f88d

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

This PR includes changesets to release 1 package

Name	Type
clerk	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

coderabbitai · 2026-04-22T15:19:08Z

📝 Walkthrough

Walkthrough

This change modifies the behavior of the clerk env pull command for Next.js projects. When no environment file exists, the command now defaults to writing pulled environment variables to .env.local instead of .env, aligning with Next.js's local secrets convention. If .env already contains existing keys, the command continues writing to .env. The change includes updates to the framework configuration in FRAMEWORK_MAP, corresponding test assertions across unit and integration tests, and Changesets metadata documentation.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating `clerk env pull` to default to `.env.local` for Next.js projects, which is clearly reflected across all modified files and test updates.
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	The pull request description clearly explains the changes: updating `clerk env pull` behavior for Next.js projects to default to `.env.local`, maintaining backward compatibility, and fixing documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

dmoerner approved these changes Apr 22, 2026
View reviewed changes

kylemac merged commit 8a825dd into mainApr 22, 2026
10 checks passed

kylemac deleted the rafa-thayto/env-pull-next branch April 22, 2026 16:40

github-actionsBot mentioned this pull request Apr 22, 2026
ci(repo): Version Packages #181
Merged