chore: prepare Voltaire production releases - #393
Draft
roninjin10 wants to merge 8 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Scaffold docs/ as a vocs 2.7.2 site (src/pages) with 22 pages: landing, introduction, installation, getting started, ecosystem, nine guides, four native/multi-language pages, and four reference pages. Every code sample was executed against the built @tevm/voltaire package, the Zig examples, or a compiled C program; pasted outputs are real. Known API defects (this-bound Abi/Legacy functions, lowercase Siwe address, KZG unavailable in portable JS) are documented rather than papered over. Adds docs to the pnpm workspace and a docs/vercel.json for a Vercel project rooted at docs/ (vocs emits Build Output API v3 when VERCEL is set). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Author
Docs site (vocs 2.7.2) — added in dcbdcbfScaffolded
Verification actually run (real output pasted into the pages):
Known API defects documented rather than hidden (each needs a code fix, not a docs fix):
Deploy target is Note: Claude AI assistant, not @roninjin10 or @fucory |
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
@tevm/voltaire0.4.1@tevm/voltaire-only publisher using npm provenancevoltaire.tevm.shPublish target and version
The consumer release target is npm package
@tevm/voltaire. Registry verification on 2026-07-29 found:voltaire@0.0.1is an unrelated “smart documentation” package@tevm/voltaire@0.4.0is the existing Voltaire package@evmts/voltairereturns npm E404cargo search '^voltaire$'returns no exact crate; this repository's Cargo package explicitly exists only to build internal crypto wrappersZig consumers continue to use the repository through
build.zig.zon; prebuilt native libraries remain CI artifacts rather than platform-specific npm packages. The portable JavaScript/WASM package is the correct first production target.The changeset chooses
0.4.1, an honest patch over the existing npm0.4.0beta rather than resetting to0.0.0or declaring an unsupported1.0.0. The package-qualified GitHub release tag will be@tevm/voltaire@0.4.1, avoiding the repository's existing genericv0.4.1tag.Real verification output
13/13 steps succeeded19/19 steps succeeded; 91/91 tests passed4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered outTest Files 1060 passed | 3 skipped (1063);Tests 22288 passed | 260 skipped (22548);Type Errors no errorsTest Files 1 passed (1);Tests 40 passed | 1 skipped (41);Type Errors no errorsdarwin-arm64,darwin-x64,linux-x64,win32-x64, packaged artifact)VERCEL=1npm audit --omit=devreported 0 vulnerabilitiesnpm pack, andgit diff --checkcompleted successfullyRelease gate
After this draft PR is reviewed and merged, Changesets creates a version PR for
@tevm/voltaire0.4.1. Publishing only occurs after a human reviews and merges that version PR. The publisher refuses to run outside GitHub Actions onmain, checks the registry to avoid duplicate publication, publishes only@tevm/voltaire, requests public access and provenance, and creates a package-qualified GitHub release only after a real publish. No manual publish was run.Known external and pre-existing blockers
Vercel – voltairefails because that Vercel project is configured with Root Directoryplayground; it must be changed todocsVercel – distinvokes the whole recursive workspace build on a 4-core/8 GB builder and exits 137; the legacy check must be disabled or scoped appropriatelyvoltaire.tevm.shcurrently serves the older Mintlify project and must be assigned to the new Vocs Vercel project after deployment is fixed.d.tsdeclarations; runtime ESM and CommonJS smoke tests passkeccak_wrapper.hinclude path), and voltaire-effect typecheck/tests (Effect platform resolution and incomplete lane); these are not represented as passing