Conversation
|
🚅 Deployed to the rivet-pr-4299 environment in rivet-frontend
|
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
PR ReviewSummary: Removes the Change AnalysisThe change itself is straightforward and appears correct. Searching the repo confirms The remaining Issues / Suggestions1. PR description is empty 2. Draft status + non-main base branch 3. No pnpm cache step (pre-existing) VerdictThe actual code change is correct and safe. The one-line removal cleans up a stale filter referencing a package that no longer exists. Before merging: fill in the PR description and confirm the base branch target is intentional. |

Description
Removed the
@rivetkit/example-registrypackage exclusion from the turbo build:publish command in the pkg-pr-new workflow. The build command now includes the example-registry package while still excluding the mcp-hub package.Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist: