Skip to content

docs: re-verify the client-library page at wharfkit antelope 1.2.0 - #18

Merged
robrigo merged 1 commit into
mainfrom
docs/wharfkit-1-2-0
Aug 18, 2026
Merged

docs: re-verify the client-library page at wharfkit antelope 1.2.0#18
robrigo merged 1 commit into
mainfrom
docs/wharfkit-1-2-0

Conversation

@robrigo

@robrigo robrigo commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

What this change claims, in one sentence:

Every fact on reference/wharfkit.md holds at @wharfkit/antelope 1.2.0, so only the pin moves.

Source: npm tarballs of @wharfkit/antelope 1.1.1 and 1.2.0, full-tree diff: the only source change is send_transaction2 exception handling (src/api/v1/chain.ts, src/api/v1/types.ts), and every file behind the page's facts (src/chain/authority.ts:82-92 with the @attention note at :84, src/chain/private-key.ts:106-112, src/chain/public-key.ts:88-98, src/api/v1/chain.ts:292-312,347-354) is byte-identical between the versions.

Tier: source-read, unchanged.

Row in reference/validation.md updated: yes; the row and the pinned-baselines line read 1.2.0 and the row records the diff scope. The CHANGELOG section assumes this merges after #17; expect a trivial conflict on CHANGELOG.md and AGENTS.md line 67 once #17 lands, which I will rebase away.

The page pinned 1.1.1 while 1.2.0 is the published release the platform installs, and its own text demands a re-check on upgrade. The 1.1.1 to 1.2.0 source diff is confined to send_transaction2 exception handling, so every fact holds and only the pin moves.
@robrigo
robrigo force-pushed the docs/wharfkit-1-2-0 branch from 26e122c to 3b9e5fb Compare August 18, 2026 21:55
@robrigo
robrigo deployed to wax-testnet August 18, 2026 21:55 — with GitHub Actions Active
@robrigo
robrigo merged commit 10bcf09 into main Aug 18, 2026
10 checks passed
@robrigo
robrigo deleted the docs/wharfkit-1-2-0 branch August 18, 2026 21:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant