Uh oh!
There was an error while loading. Please reload this page.
fix: update changesets fixed group for the trigger-* rename - #1754
Merged
Conversation
The Release workflow's fixed-group verifier requires the group to match the public workspace exactly; swap the renamed trigger package names. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release workflow's fixed-group verifier (scripts/check-changeset-fixed.mjs) failed after #1749/#1751: the group still listed the old plugin-trigger-* names. Swapped for @objectstack/trigger-record-change and @objectstack/trigger-schedule; verifier passes locally.
🤖 Generated with Claude Code