release: @parity/truapi 0.16.0, @parity/truapi-host 0.13.0 - #744
Open
tommyldev wants to merge 1 commit into
Open
release: @parity/truapi 0.16.0, @parity/truapi-host 0.13.0#744tommyldev wants to merge 1 commit into
tommyldev wants to merge 1 commit into
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
CI Status: 14 required jobs green, 13 passed and 1 skipped by path filter. All job results
Commit |
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.
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 onmain.Summary
This PR publishes
@parity/truapi0.16.0 and@parity/truapi-host0.13.0 to npm, along with the prebuilttruapi-hostbinaries. 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
mainalready carries. The PR consumes the one changeset left behind after #732:temporary-unwatermarked-signing.md, minor onboth packages
Why 0.16.0 / 0.13.0. Both earlier
Releaseruns failed at Verify release manifests because a changeset from anotherPR 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.
mainmanifests already read 0.15.0 / 0.12.0, so consuming #731's minorchangeset 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.mdfolds them all into 0.16.0 because it keys sections off tags. Therelease-clijobpublishes the prebuilt
truapi-hostbinaries under 0.16.0, the first stable installer build containing #627.Not included.
@parity/ios-hostand@parity/android-host, as in #732; a follow-uprelease:PR naming them is theway to cut them.
@parity/truapi-debuggermoved to 0.1.3 as an internal-dependency side effect and stays unpublished.Before merging. Please rebase this branch on
mainimmediately before enqueueing and confirm.changeset/holds onlyconfig.jsonat that moment. Both earlier attempts died to a changeset-carrying PR entering the queue just ahead of therelease 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 onlyconfig.json,scripts/cut-version.shsnapshot written under0.16.0,Cargo.lockupdated to 0.16.0 for both crates.Checklist
npm run changesetand selected the package + bump type (patch / minor / major) — the changeset was already onmain(temporary-unwatermarked-signing.md, from feat(signing): add temporary deprecated unwrapped signing #731)npm run version-packagesto consume the changesetjs/packages/truapi/package.jsonversion is bumpedjs/packages/truapi-host/package.jsonversion is bumped when releasing the host@parity/ios-host <version>when publishing the iOS host — n/a, npm packages onlyPackage.swift— n/a@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-hostdepends on^<current @parity/truapi version>js/packages/truapi/CHANGELOG.mdhas the new entryjs/packages/truapi-host/CHANGELOG.mdhas the new entry when releasing the hostrust/crates/truapi/Cargo.tomlandrust/crates/truapi-host-cli/Cargo.tomlversions matchjs/packages/truapi/package.json(npm run check-release-versions), andCargo.lockrecords them@parity/truapialso publishes the prebuilttruapi-hostbinaries; no extra title entry is needed.changeset/(other thanconfig.json)