Skip to content

ci: remove broken changeset-bot workflow in favor of GitHub App#373

Merged
kimyouknow merged 1 commit intomainfrom
chore/remove-changeset-bot-workflow
Apr 21, 2026
Merged

ci: remove broken changeset-bot workflow in favor of GitHub App#373
kimyouknow merged 1 commit intomainfrom
chore/remove-changeset-bot-workflow

Conversation

@kimyouknow
Copy link
Copy Markdown
Collaborator

Summary

Removes the broken .github/workflows/changeset-bot.yml workflow. The changesets/bot repository is a Probot-based GitHub App (deployed as a Next.js app on Vercel), not a reusable GitHub Action. It has no action.yml or Dockerfile, so uses: changesets/bot@<ref> has been failing since it was introduced.

Root cause timeline

PR Change Result
#350 Added uses: changesets/bot@v1 v1 tag does not exist → failed from day one
#363 Changed to @<master SHA> SHA resolved, but Can't find action.yml / Dockerfile

Verified via the repo tree — changesets/bot ships only these:

app.yml                  ← Probot app manifest
pages/api/webhook.ts     ← Next.js webhook handler
index.ts                 ← Probot entry
package.json
(no action.yml, no Dockerfile)

Global code search (gh search code "changesets/bot") returned only this repository using uses: changesets/bot@*. No other project uses this pattern — the README explicitly directs to install the GitHub App.

Replacement

The changeset-bot GitHub App has been installed on @toss with access to toss/react-simplikit. The App will automatically comment on every PR about changeset status — same behavior the broken workflow was trying to replicate.

App install URL: https://github.com/apps/changeset-bot

Scope

  • 1 file deleted: .github/workflows/changeset-bot.yml
  • No other workflow affected
  • Unrelated to changesets/action@v1.7.0 used in release.yml (that is a real action and works correctly)

Test plan

  • After merge, open a test PR without a changeset → verify the App comments "You need to add a changeset..."
  • Open a test PR with a changeset → verify the App comments "This PR includes changesets"
  • Confirm the bot check column no longer appears on PRs

The changesets/bot repository is a Probot-based GitHub App, not a
reusable GitHub Action. It ships with app.yml / pages/api/webhook.ts
rather than action.yml, so 'uses: changesets/bot@<ref>' has been
failing ever since #350 introduced it.

- PR #350 used '@v1' (tag does not exist) → failed from day one
- PR #363 changed to '@<master SHA>' → resolved the SHA but still
  failed because the repo has no action.yml / Dockerfile

Correct usage is documented in the project README: install the
GitHub App from https://github.com/apps/changeset-bot. The App has
now been installed on the @toss organization with access to
toss/react-simplikit and will comment on PRs automatically, making
this workflow redundant.

Removing this file unblocks the 'bot' check column on every PR.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 21, 2026

⚠️ No Changeset found

Latest commit: 3e999f5

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

@github-actions
Copy link
Copy Markdown
Contributor

Size Change: 0 B 🆕

Total Size: 0 B

compressed-size-action

@kimyouknow kimyouknow marked this pull request as ready for review April 21, 2026 14:21
@kimyouknow kimyouknow requested a review from zztnrudzz13 as a code owner April 21, 2026 14:21
@kimyouknow kimyouknow merged commit 30c029e into main Apr 21, 2026
11 of 12 checks passed
@kimyouknow kimyouknow deleted the chore/remove-changeset-bot-workflow branch April 21, 2026 14:21
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