Skip to content

chore(repo): remove backported changesets and backfill core-2 changelogs#7847

Open
jacekradko wants to merge 2 commits intomainfrom
jacek/remove-backported-changesets
Open

chore(repo): remove backported changesets and backfill core-2 changelogs#7847
jacekradko wants to merge 2 commits intomainfrom
jacek/remove-backported-changesets

Conversation

@jacekradko
Copy link
Member

@jacekradko jacekradko commented Feb 13, 2026

Summary

  • Remove 33 changeset files from main that were already consumed by the release/core-2 release process, preventing duplicate changelog entries when core-3 releases
  • Backfill 18 package CHANGELOGs with version entries published on core-2 that were missing from main (e.g., @clerk/clerk-js 5.114.1–5.123.0)

Closes: USER-4423

Context

Commits were previously backported (cherry-picked) from main to release/core-2, carrying their changeset files along. Core-2's release process consumed those changesets, but the same files still existed on main. Without this cleanup, a core-3 release would consume them again, creating duplicate changelog entries.

Additionally, core-2 published many versions that main's CHANGELOGs didn't include. These are now backfilled so the changelogs on main have a complete history.

Packages with backfilled CHANGELOGs (18)

agent-toolkit, astro, backend, chrome-extension, clerk-js, expo-passkeys, expo, express, fastify, localizations, nextjs, nuxt, react-router, react, shared, tanstack-react-start, testing, vue

Test plan

  • pnpm build passes
  • Spot-checked CHANGELOG formatting (clerk-js, nextjs, shared) — entries inserted at correct position with proper formatting
  • git diff main --stat shows only 33 changeset deletions + 18 CHANGELOG updates (51 files)

Summary by CodeRabbit

  • Chores
    • Removed 40+ changeset entries across multiple packages.
    • Updated CHANGELOG files for 15+ packages with new version entries and patch/minor changes.
    • Documented dependency updates and bug fixes across various package releases, including clerk-js, backend, shared, react, astro, and others.

Remove 33 changeset files that were already consumed by the core-2
release process to prevent duplicate changelog entries on the next
core-3 release. Backfill 18 package CHANGELOGs with version entries
published on core-2 that were missing from main.
@changeset-bot
Copy link

changeset-bot bot commented Feb 13, 2026

⚠️ No Changeset found

Latest commit: 54b15af

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Feb 13, 2026

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

Project Deployment Actions Updated (UTC)
clerk-js-sandbox Ready Ready Preview, Comment Feb 13, 2026 9:28pm

Request Review

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 13, 2026

📝 Walkthrough

Walkthrough

This pull request performs a bulk release consolidation across the Clerk monorepo by removing approximately 35 pending changeset files and updating multiple package CHANGELOG.md files with new version entries. The changeset removals correspond to accumulated fixes, features, and dependency updates that have been consolidated into versioned releases (e.g., @clerk/backend 2.31.0, @clerk/clerk-js 5.123.0, @clerk/shared 3.45.0). The CHANGELOG updates document patch and minor version changes along with dependency version bumps across packages including clerk-js, backend, react, shared, nextjs, expo, and others. No source code modifications are present—only release metadata and documentation updates.

Possibly related PRs

🚥 Pre-merge checks | ✅ 5 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Linked Issues check ❓ Inconclusive The linked issue provides minimal context with only a title and vague description; the PR objectives clearly state the changes but the issue lacks detailed requirements to validate against. The linked issue should include specific acceptance criteria or requirements to enable proper compliance validation of the changeset.
✅ Passed checks (5 passed)
Check name Status Explanation
Out of Scope Changes check ✅ Passed All changes are within scope: 33 changeset deletions and 18 CHANGELOG updates across affected packages, with no unrelated modifications detected.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title clearly and concisely summarizes the main changes: removing backported changesets and backfilling CHANGELOGs. It is specific, relevant, and accurately represents the primary objectives of the changeset.

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

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • CORE-2: Entity not found: Issue - Could not find referenced Issue.

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@packages/backend/CHANGELOG.md`:
- Around line 3-15: The changelog lists two functional changes (addition of
providerUserId on ExternalAccount and the new createBulk() method on
WaitlistEntryAPI), so verify whether corresponding behavior changes exist in
code and add/update tests accordingly: if ExternalAccount now exposes
providerUserId or deprecates externalId, add unit/integration tests for the
ExternalAccount model/serializers and any API endpoints that surface the field
(search for ExternalAccount and providerUserId); if
WaitlistEntryAPI.createBulk() was implemented, add tests covering bulk creation
success, validation/failure paths, and edge cases by locating the
WaitlistEntryAPI class and its createBulk method; finally, update test suites
and CI config to run the new tests and include references to the new tests in
the PR.

In `@packages/react-router/CHANGELOG.md`:
- Around line 3-12: The changelog release notes list dependency updates (e.g.,
`@clerk/shared`, `@clerk/backend`, `@clerk/clerk-react`, `@clerk/types`) but the PR
contains no tests; add or update automated tests that exercise the behavioral
changes introduced by these dependency bumps—identify the changed behaviors in
the code that depend on the updated packages (for example components/hooks in
the react-router package that integrate with `@clerk/clerk-react` or types from
`@clerk/types`), create unit/integration tests exercising those code paths, and
include them in the test suite so the release (2.4.4) is covered by tests before
merging.

@jacekradko jacekradko changed the title chore: Remove backported changesets and backfill core-2 CHANGELOGs chore(repo): remove backported changesets and backfill core-2 changelogs Feb 13, 2026
@pkg-pr-new
Copy link

pkg-pr-new bot commented Feb 13, 2026

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@7847

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@7847

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: 54b15af

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant