fix(rivetkit): pack inspector in pkg-pr-new#4409
Open
NathanFlurry wants to merge 1 commit intomainfrom
Open
Conversation
Co-authored-by: Codex <codex@openai.com>
|
🚅 Deployed to the rivet-pr-4409 environment in rivet-frontend
|
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Align the
pkg-pr-newworkflow with the release pipeline for RivetKit inspector packaging.The workflow now builds publishable RivetKit packages with the release exclusions and then runs
build:pack-inspectorexplicitly so the real inspector frontend is bundled before preview publishing.Type of change
How Has This Been Tested?
Compared the workflow steps against the release scripts and reviewed the resulting PR diff.
Ran
npx turbo run build:pack-inspector -F rivetkit --dry=jsonto confirm the pack step still depends on@rivetkit/engine-frontend#build:inspector.Did not run the full build or publish pipeline.
Checklist: