ci(repo): Scope core-2 release dispatch to sdk-infra-workers - #8741
Conversation
The release/core-2 maintenance branch was dispatching workflows to clerk/dashboard and clerk/clerk-docs, which have moved on to Core 3. Those dispatches now 404/403 and, because the calls were fire-and-forget promises with no continue-on-error, the rejection failed the whole Release job. Keep only the sdk-infra-workers clerk-js CDN version bump, await it, and mark the step continue-on-error so a post-publish notification failure can't fail a release that already shipped to npm.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 9882feb The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen 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 |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/elements
@clerk/clerk-expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/clerk-react
@clerk/react-router
@clerk/remix
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/themes
@clerk/types
@clerk/upgrade
@clerk/vue
commit: |
The Release (Core 2) job was failing on "Trigger workflows on related repos".
release/core-2is a maintenance branch, but it was still dispatchingprepare-nextjs-sdk-update.ymltoclerk/dashboardandtypedoc-core-2.ymltoclerk/clerk-docs, both of which have moved on to Core 3. Those dispatches now return 404 / 403, and since the calls were fire-and-forget promises with no error handling, the rejection bubbled up as an unhandled error and failed the whole job (whichmaindoesn't hit because its version of this step was already hardened).This keeps only the
sdk-infra-workersclerk-js CDN version bump,awaits it instead of firing-and-forgetting, and marks the stepcontinue-on-error: trueso a downstream-notification hiccup can't fail a release that already published to npm.Failing run: https://github.com/clerk/javascript/actions/runs/26906104288