Skip to content

chore: bump version to 0.33.0#155

Closed
roscoe-infinex wants to merge 1 commit into
nktkas:mainfrom
roscoe-infinex:chore/bump-0.33.0
Closed

chore: bump version to 0.33.0#155
roscoe-infinex wants to merge 1 commit into
nktkas:mainfrom
roscoe-infinex:chore/bump-0.33.0

Conversation

@roscoe-infinex

Copy link
Copy Markdown
Contributor

What this does

Bumps deno.json version 0.32.20.33.0 (the single source of truth for both the JSR and npm publishes).

Why minor, not patch

Per the SDK's own policy (README.md §Versioning): pre-1.0.0, breaking changes bump the minor, everything else bumps the patch — with the sole exception that breaks in the request/response/event types mirroring the Hyperliquid API ship as patch (the break comes from Hyperliquid, not the SDK).

There are 11 !-marked breaking commits since v0.32.2, and most break the SDK's own surface (outside that exception), so a minor is required:

Suggested release notes (for the v0.33.0 GitHub Release)

What's Changed

Breaking

Features

Fixes / deps

  • fix(mod): expose AbstractWalletError from the main import
  • build(deps): bump @valibot/valibot, @nktkas/rews, @std/msgpack, @noble/hashes

Full Changelog: v0.32.2...v0.33.0

After merge, the release path is unchanged: cut a v0.33.0 GitHub Release → publish_jsr.yml + publish_npm.yml fire on release: published and publish via OIDC (npm dist-tag latest, since the version has no prerelease suffix).

Breaking changes since v0.32.2 (signing, transport, utils, subscription,
build/ESM-only) require a minor bump per the SDK versioning policy (pre-1.0.0:
breaking changes bump minor).
@nktkas nktkas closed this Jun 20, 2026
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.

2 participants