chore(changeset): add patch changeset to unblock the canary release#69
Merged
Conversation
The canary workflow (`changeset version --snapshot canary`) no-ops when there are no pending changesets — it exits with 'No unreleased changesets found' and skips publishing because 9.30.0 is already on npm (that is why the last Release run was green but published nothing; the canary dist-tag is still the 15-Jul 9.30.0-canary snapshot). Add a patch changeset covering the merged-but-unreleased fixes on main since 9.30.0 (#53 SDK-6882 setCustomTags type, #54 reloadSession session-id refresh). This lets 'changeset version --snapshot canary' compute 9.30.1-canary-<ts> and publish it. (A changeset was previously removed in 0f9d1f0 'remove changeset file (review feedback)', which is what left main with none.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
osho-20
approved these changes
Jul 21, 2026
pri-gadhiya
approved these changes
Jul 21, 2026
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
4 participants
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.
Why
The last
Release(canary) run was green but published nothing.changeset version --snapshot canaryhit "No unreleased changesets found, exiting", so no snapshot version was computed;changeset publishthen skipped because9.30.0is already on npm. Net: thecanarydist-tag is still9.30.0-canary-20260715111942(15 Jul) — no fresh canary.Root cause: no pending changeset on
main. A changeset was previously removed in0f9d1f0("remove changeset file (review feedback)"), so the merged-but-unreleased work since 9.30.0 has no changeset to snapshot from.What
Adds a single patch changeset covering the unreleased fixes on
mainsince 9.30.0:reloadSession(Test Observability keeps linking to the correct session after a reload).browser.setCustomTagson theWebdriverIO.Browsertype so it type-checks in consumer projects.(#57 is CI-only — PR-review workflows — so it's intentionally not in the changeset.)
Effect
Release(canary) dispatch computes9.30.1-canary-<datetime>(viasnapshot.useCalculatedVersion: true) and publishes it under thecanarydist-tag.9.30.1when the "Version Packages" PR is merged (publish stays manual — this PR does not release tolatest).Note for reviewers
Please confirm these two fixes are intended for the next release. If the earlier changeset was removed to defer them, hold this; if it was removed by accident, this restores the release path. Bump is
patch(both are fixes, no new API) — bump tominorif you'd rather.🤖 Generated with Claude Code