fix: publish secure-exec vfs crates#116
Merged
Merged
Conversation
railway-app
Bot
temporarily deployed
to
secure-exec / secure-exec-pr-116
June 23, 2026 15:25
Destroyed
railway-app
Bot
temporarily deployed
to
rivet-frontend / secure-exec-pr-116
June 23, 2026 15:25
Destroyed
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
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.
Summary\n- restore the crates/vfs package name to secure-exec-vfs-core for crates.io\n- keep the workspace alias as vfs via package = "secure-exec-vfs-core"\n- include secure-exec-vfs-core and secure-exec-vfs in the crates.io publish order\n- make the version bumper handle package/path/version inline tables\n\n## Validation\n- pnpm --dir scripts/publish test\n- cargo metadata shows secure-exec-vfs-core and secure-exec-vfs workspace packages\n