chore(release): prepare OpenPI 0.8.0 - #481
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.
Current main contains 15 commits since v0.7.0, including Web authentication and trust diagnostics, runtime inspection, archived Session recovery, inspectable prompt/tool-call trajectories, and startup/model-selection fixes. Prepare 0.8.0 so these changes can ship through the existing tagged npm release workflow.
Only package.json changes from 0.7.0 to 0.8.0. The lockfile has no root version field. Runtime code, dependencies and committed Web assets are unchanged by this PR.
Validation: local
bun run checkpassed;bun run testpassed (1,461 Node tests passed, one platform skip; 113 Vitest tests passed). Exact PR head2ba63d7889560c756cfb96a044c42fb82cbb1b83passed Node 22/24/26, Windows and Web E2E CI: https://github.com/openpi-dev/openpi/actions/runs/34176175953.The candidate tarball contains 232 files, including the Web assets, CLI and third-party notices. A fresh isolated install with lockfile-selected Pi peers passed unique-source
pi list, offline RPC extension discovery, Web static assets, unauthenticated API rejection (401), authenticated snapshot (200), and graceful shutdown. No model call was made. Candidate integrity:sha512-3KxmKwwK9y08ShVw1p9TZGwKqn7hsYpZlyk0wG9MbWwxyDQQbJs4//77yssfhL7cnWwX0Y/HCinGf7pMlLc33A==.The user explicitly authorized administrator merge after the normal SHA-guarded merge was rejected for the missing approving review. Merged at
993fd8e22ff5c7495c1b5c19f9d64c0b6b97c252;v0.8.0points to that commit.Published OpenPI 0.8.0 and npm 0.8.0, with latest set to 0.8.0. Tagged Release workflow passed. The downloaded npm tarball is byte-identical to its CI artifact; registry signature and Sigstore SLSA provenance verified against the release workflow, tag and commit. Published integrity:
sha512-fUHztbcChJrnwLjuLp7UlduGySGpL4QlR0VLMvZd0mllqc9MASFKD+LQcBYB8eVdImLL/qxJC3otph2f8fBTBQ==. All 232 file contents match the locally tested candidate.Repeated the isolated install smoke using the registry tarball: unique Pi source, offline RPC extension discovery, Web assets, API auth (401/200), and graceful shutdown all passed. No live model call was made. Existing local Pi installations were not updated.