[Chore] Version packages to 0.7.0 - #124
Merged
Merged
Conversation
Consumes the twenty pending changesets as a lockstep minor: 0.6.0 -> 0.7.0 across the fixed group, bridge 0.4.2 -> 0.4.3, and the core version constant synced by `scripts/sync-versions.mjs`. Unlike 0.6.0, the number did not have to be held by hand. That release recorded "changesets resolved the release as 1.0.0 because the workspace:^ peer ranges on veil-core make any 0.x minor out-of-range for peer dependents". Those ranges are now `workspace:>=0.6.0 <1.0.0`, so a 0.x minor stays inside them, `onlyUpdatePeerDependentsWhenOutOfRange` leaves the peer dependents alone, and `changeset version` produces the intended minor on its own. What ships, in short: the shield-swap CLI as its own package; blinded-identity reservation, tracking and recovery; `previewMint`, `planSwap`, `tokenData`, `listTokens`, `liquidityForAmount`, and typed unit converters; per-network DEX API hosts; the Q128 helpers on options objects with their positional forms deprecated; `SHIELD_WRAPPERS` removed; a one-minute confirmation default; and Provable API authentication in veil-aleo-sdk. Verified before tagging: `pnpm build` clean, `pnpm -r exec tsc --noEmit` clean, 1475 tests passing. Tarballs checked by packing rather than by inspection — the `workspace:` protocol resolves to `>=0.6.0 <1.0.0` in the published peerDependencies, and the shield-swap tarball carries 27 files with no state file or credentials among them.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Consumes the twenty pending changesets as a lockstep minor: 0.6.0 → 0.7.0 across the fixed group,
veil-aleo-bridges0.4.2 → 0.4.3, andpackages/core/src/version.tssynced byscripts/sync-versions.mjs.The number came out right on its own this time
0.6.0 recorded: "changesets resolved the release as 1.0.0 because the
workspace:^peer ranges on veil-core make any 0.x minor out-of-range for peer dependents; the release number is manually held at the intended minor."Those ranges are now
workspace:>=0.6.0 <1.0.0, so a 0.x minor stays inside them,onlyUpdatePeerDependentsWhenOutOfRangeleaves the peer dependents alone, andchangeset versionproduces 0.7.0 with no manual correction. Verified both ways before committing: with the old ranges the plan was major for all nine, with the new ones it is minor.What ships
@provablehq/shield-swap-clias its own package — the trader scripts extracted, with colour,-hon every subcommand, and--jsonon every path including errorspreviewMint,planSwap,tokenData,listTokens,liquidityForAmount,parseUnits/formatUnitsSHIELD_WRAPPERSremoved — it had no caller and duplicated on-chain stateveil-aleo-sdkVerification
pnpm buildpnpm -r exec tsc --noEmitpnpm vitest runTarballs checked by packing rather than by reading the manifests: the
workspace:protocol resolves to>=0.6.0 <1.0.0in the publishedpeerDependencies, and the shield-swap tarball carries 27 files with no state file or credentials among them.Publishing
Not done here —
pnpm releaserunspnpm build && changeset publishlocally and this machine is not authenticated to npm (npm whoami→ 401). Merge this, then publish from an authenticated shell.