Version Packages - #101
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 27, 2026 12:07
3416434 to
d560255
Compare
AakashHotchandani
approved these changes
Jul 27, 2026
hamza-browserstack
approved these changes
Jul 27, 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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@wdio/browserstack-service@9.32.1
Patch Changes
aefd604: - Fixed a statically-skipped test (
it.skip) being left orphaned as "in progress" on the Test Observability dashboard in the CLI flow. Such tests are reported from the un-awaitedonTestSkipreporter hook, so theirTestRunFinishedevent could still be pending when the worker tore down; theafter()hook now drains these skip reports before the session closes so the test is correctly reported as skipped.1a973e9: - fix: Accessibility command wrapping.
a24973b: - Fixed Test Observability not being fully disabled for a run when the build could not be started (e.g. an unsupported framework) — such sessions no longer emit observability events or get linked to a non-existent build.
8539e5f: fix(a11y): restore per-command auto-scanning for App Automate accessibility sessions
App Automate accessibility sessions were skipped by the per-command
overwriteCommandwrapping in
onBeforeExecute(guarded to!isAppAccessibility), so app a11y scans onlyfired via an explicit
performScan()or the end-of-test lifecycle scan — per-commandauto-scanning that web sessions get was effectively disabled for app. Command wrapping now
applies to app sessions too, with each
overwriteCommandcall individually guarded so acommand the appium driver does not register is skipped (logged at debug) instead of aborting
onBeforeExecute. Commands appium does register (click,setValue, ...) now auto-scan onApp Automate, matching the web flow.