Skip to content

fix(release): Run CI on release branches for Craft artifacts#92

Merged
dcramer merged 1 commit intomainfrom
dcramer/craft-artifact-fix
Feb 3, 2026
Merged

fix(release): Run CI on release branches for Craft artifacts#92
dcramer merged 1 commit intomainfrom
dcramer/craft-artifact-fix

Conversation

@dcramer
Copy link
Member

@dcramer dcramer commented Feb 3, 2026

Craft publish fails when it can't find npm artifacts for the release commit. The root cause is that CI only ran on main, but craft prepare creates release commits on release/* branches, so no artifacts were uploaded for those commit SHAs.

This matches the approach used by sentry-mcp: run CI on both main and release/* branches so artifacts are uploaded when release commits are pushed.

The previous fix (#91) added artifact upload to CI, which was correct. This ensures CI actually runs on release commits.

Fixes the "Can't find any artifacts" error during craft publish.

CI uploads artifacts keyed by commit SHA, but craft prepare creates
release commits on release/* branches. Without CI running on those
branches, no artifacts exist for the release commit SHA, causing
craft publish to fail.

Matches sentry-mcp's approach: run CI on both main and release/*
branches so artifacts are uploaded for release commits.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Feb 3, 2026

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

Project Deployment Actions Updated (UTC)
warden Ready Ready Preview, Comment Feb 3, 2026 11:53pm

Request Review

@dcramer dcramer merged commit 5282fb9 into main Feb 3, 2026
13 checks passed
@dcramer dcramer deleted the dcramer/craft-artifact-fix branch February 3, 2026 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant