chore(release): 0.5.0 - #339
Merged
Merged
Conversation
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.
Summary
@tt-a1i/openpifrom0.4.0to0.5.0/weblaunchermainopenpi web <workspace>CLI contract while/webstarts an independent browser-owned workspaceThis is a minor release because the public feature surface has expanded since 0.4.0; it is not only a patch set.
Release gates
mainCI at51b85ad: passedbun run check: passedbun run test: 1235 Node tests passed, 1 skipped; 30 Vitest tests passednpm pack --dry-run --json --ignore-scripts:@tt-a1i/openpi@0.5.0, 176 files, 686,335 bytes compressed, 2,049,622 bytes unpackedgit diff --check: passedPublication plan
After merge, create
v0.5.0at the exact mergedmaincommit. The tag-triggered Release workflow will re-run validation, build a single npm artifact, and publish it through the protectednpmenvironment with OIDC. Publication is not complete until the workflow, npm dist-tag/provenance, GitHub Release, and clean install smoke are verified.