Skip to content

release: @parity/truapi 0.16.0, @parity/truapi-host 0.13.0 - #744

Open
tommyldev wants to merge 1 commit into
mainfrom
release/truapi-0.16.0
Open

release: @parity/truapi 0.16.0, @parity/truapi-host 0.13.0#744
tommyldev wants to merge 1 commit into
mainfrom
release/truapi-0.16.0

Conversation

@tommyldev

@tommyldev tommyldev commented Sep 12, 2026

Copy link
Copy Markdown

Release: @parity/truapi 0.16.0, @parity/truapi-host 0.13.0

Important

The PR title must start with release: for the publish workflow to fire.
Don't rewrite the squash commit subject in the merge dialog — the
release: prefix has to land on main.

Summary

This PR publishes @parity/truapi 0.16.0 and @parity/truapi-host 0.13.0 to npm, along with the prebuilt truapi-host binaries. It is the third attempt to get the post-0.13.1 protocol out: #722 and #732 both merged but never published, so the registry still stops at @parity/truapi@0.13.1 / @parity/truapi-host@0.10.1.

Nothing new is bumped beyond what main already carries. The PR consumes the one changeset left behind after #732:

Why 0.16.0 / 0.13.0. Both earlier Release runs failed at Verify release manifests because a changeset from another
PR was merged by the queue minutes ahead of the release commit (#665 ahead of #722, #731 ahead of #732; see #732 (comment)).
No 0.14.x / 0.15.x / 0.11.x / 0.12.x tags exist. main manifests already read 0.15.0 / 0.12.0, so consuming #731's minor
changeset lands on 0.16.0 / 0.13.0. The package changelogs keep the unpublished 0.14.0 / 0.15.0 entries above 0.13.1, and
the generated root CHANGELOG.md folds them all into 0.16.0 because it keys sections off tags. The release-cli job
publishes the prebuilt truapi-host binaries under 0.16.0, the first stable installer build containing #627.

Not included. @parity/ios-host and @parity/android-host, as in #732; a follow-up release: PR naming them is the
way to cut them. @parity/truapi-debugger moved to 0.1.3 as an internal-dependency side effect and stays unpublished.

Before merging. Please rebase this branch on main immediately before enqueueing and confirm .changeset/ holds only
config.json at that moment. Both earlier attempts died to a changeset-carrying PR entering the queue just ahead of the
release commit. I will keep this branch rebased until it lands.

Verified locally: npm run check-release-versions (sync-release-versions: crate manifests, host and truapi-debugger dependencies, and package-lock.json use @parity/truapi 0.16.0), .changeset/ contains only config.json,
scripts/cut-version.sh snapshot written under 0.16.0, Cargo.lock updated to 0.16.0 for both crates.

Checklist

  • Ran npm run changeset and selected the package + bump type (patch / minor / major) — the changeset was already on main (temporary-unwatermarked-signing.md, from feat(signing): add temporary deprecated unwrapped signing #731)
  • Ran npm run version-packages to consume the changeset
  • js/packages/truapi/package.json version is bumped
  • js/packages/truapi-host/package.json version is bumped when releasing the host
  • The PR title includes @parity/ios-host <version> when publishing the iOS host — n/a, npm packages only
  • Regenerated iOS bindings and container outputs are committed; CI builds and simulator-tests the XCFramework, publishes it, then commits Package.swift — n/a
  • The PR title includes @parity/android-host <version> when publishing the Android host AAR; nothing in the tree records that version, so there is no manifest to bump — n/a
  • @parity/truapi-host depends on ^<current @parity/truapi version>
  • js/packages/truapi/CHANGELOG.md has the new entry
  • js/packages/truapi-host/CHANGELOG.md has the new entry when releasing the host
  • rust/crates/truapi/Cargo.toml and rust/crates/truapi-host-cli/Cargo.toml versions match js/packages/truapi/package.json (npm run check-release-versions), and Cargo.lock records them
  • Releasing @parity/truapi also publishes the prebuilt truapi-host binaries; no extra title entry is needed
  • No leftover files under .changeset/ (other than config.json)

@tommyldev
tommyldev requested a review from a team September 12, 2026 07:01
@github-actions github-actions Bot added documentation Improvements or additions to documentation javascript Pull requests that update javascript code labels Sep 12, 2026
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​@​parity/​truapi@​0.15.0 ⏵ 0.16.0N/AN/AN/AN/AN/A

View full report

@github-actions

Copy link
Copy Markdown

CI Status: 14 required jobs green, 13 passed and 1 skipped by path filter.

All job results
job result
android-bindings success
changes success
codegen success
e2e skipped
explorer success
ios-bindings success
ios-swift success
licenses success
playground success
rust success
ts-client success
ts-debugger success
ts-host success
wasm-provider success

Commit e56abd5e · run log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant