Skip to content

ci(repo): bump break-check to v0.2.0#8793

Open
jacekradko wants to merge 1 commit into
mainfrom
jacek/break-check-0.2.0
Open

ci(repo): bump break-check to v0.2.0#8793
jacekradko wants to merge 1 commit into
mainfrom
jacek/break-check-0.2.0

Conversation

@jacekradko

@jacekradko jacekradko commented Jun 10, 2026

Copy link
Copy Markdown
Member

Bumps the pinned @clerk/break-check from 0.1.1 to 0.2.0 in the three spots in api-changes.yml: the action SHA, the break-check-version input, and the baseline snapshot step. The 0.1.2/0.2.0 releases are detector fixes; union member reorders no longer report as phantom breaking changes (clerk/break-check#85), removed or edited overloads and combined optionality-plus-type flips are now reported instead of silently collapsing, and entry points declared under nested export conditions or .d.cts files are discovered instead of skipped.

action.yml is unchanged between the two pins, and the snapshot format stamps are identical across versions, so detect@0.2.0 keeps accepting the baseline artifact built by 0.1.1 until the merge push regenerates it.

Summary by CodeRabbit

  • Chores
    • Updated internal build and API checking tooling to use latest versions for enhanced compatibility and reliability.

@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
clerk-js-sandbox Ready Ready Preview, Comment Jun 10, 2026 2:52am

Request Review

@changeset-bot

changeset-bot Bot commented Jun 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d14e696

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

This PR includes changesets to release 0 packages

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

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

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

This PR upgrades the @clerk/break-check tool from version 0.1.1 to 0.2.0 in the GitHub Actions workflow used for API change detection. The baseline snapshot generation and the break-check action configuration are both updated to use the new version, with a changeset entry documenting the upgrade.

Changes

Break-check version upgrade to 0.2.0

Layer / File(s) Summary
Update break-check version in workflow and document
.changeset/young-falcons-wave.md, .github/workflows/api-changes.yml
The @clerk/break-check tool version is updated from 0.1.1 to 0.2.0 in the baseline snapshot generation command and the GitHub Action configuration. A changeset entry is added to document this change.

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • clerk/javascript#8781: Establishes the initial @clerk/break-check integration with version 0.1.1 in the API change detection workflow that this PR upgrades to 0.2.0.

Suggested labels

actions

Suggested reviewers

  • wobsoriano

Poem

A rabbit hops through versions bright,
From 0.1 to 0.2 in flight,
With changelog singing in the breeze,
API checks now aim to please! 🐰✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: bumping the @clerk/break-check dependency from v0.1.1 to v0.2.0 in the CI workflow configuration.
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.

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


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

@pkg-pr-new

pkg-pr-new Bot commented Jun 10, 2026

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/hono

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

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

@clerk/upgrade

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

@clerk/vue

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

commit: d14e696

@github-actions

Copy link
Copy Markdown
Contributor

API Changes Report

Generated by Break Check on 2026-06-10T02:54:44.487Z

Summary

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

Note
Break Check could not snapshot 3 subpaths; the diff below excludes them.

  • @clerk/astro ./env: Internal Error: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.
  • @clerk/shared ./cookie: Internal Error: Unable to follow symbol for "Cookies" You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.
  • @clerk/testing ./cypress: Symbol not found for identifier: Cypress

No API Changes Detected

All packages have stable APIs with no detected changes.


Report generated by Break Check

Last ran on d14e696.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/api-changes.yml:
- Around line 175-177: The workflow currently pins clerk/break-check using the
SHA "1601551787d9ce47c22a9bfc95ba4ba1ea6afb19" while also specifying
break-check-version: '0.2.0'; update the action reference so it matches the
actual v0.2.0 commit (replace the pinned SHA with
6884d82b57f1b9a69a354a1f8af57e63710c88fa) or alternatively switch the action
reference to the tag form clerk/break-check@v0.2.0; ensure the uses line (the
clerk/break-check@... entry) and/or the break-check-version remain consistent.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 77b2b3ac-788d-43c6-8b1f-1f4241df2d83

📥 Commits

Reviewing files that changed from the base of the PR and between 400d10c and d14e696.

📒 Files selected for processing (2)
  • .changeset/young-falcons-wave.md
  • .github/workflows/api-changes.yml

Comment thread .github/workflows/api-changes.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant