Skip to content

Feat/skip app override v8 - #102

Open
hamza-browserstack wants to merge 2 commits into
sdk_v8_pre_prodfrom
feat/skip-app-override-v8
Open

Feat/skip app override v8#102
hamza-browserstack wants to merge 2 commits into
sdk_v8_pre_prodfrom
feat/skip-app-override-v8

Conversation

@hamza-browserstack

Copy link
Copy Markdown
Contributor

What is this about?

Related Jira task/s

Release (mandatory for every PR — required for the ready-for-review label)

Version bump: (required — tick exactly one)

  • minor (backwards-compatible feature)
  • patch (bug fix or other small change)

Release notes type: (optional)

  • New Feature
  • Bug Fix
  • Other Improvement

Release notes (customer-facing): (optional but encouraged)

Release notes (internal): (required — engineer-facing; what actually changed / why)

Checklist

  • Ready to review
  • Has it been tested locally?

PR Validations

Run Tests: Comment RUN_TESTS to trigger sanity tests.

Bhargavi-BS and others added 2 commits July 15, 2026 19:53
Port of webdriverio/webdriverio#15374 (v8 backport of #15373) to the
standalone repo.

With skipAppOverride: true the service classifies the session as App
Automate even when no app option is set, skips the app upload, and does
not inject an appium:app capability — the user supplies the app
reference themselves. Conflicting app option is warned about and
ignored; skipAppOverride: false with no app fails fast before any
session starts. The option is stripped from bstack:options and never
forwarded to the hub.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@hamza-browserstack
hamza-browserstack requested a review from a team as a code owner July 27, 2026 17:30
@hamza-browserstack
hamza-browserstack requested review from 07souravkunda and Bhargavi-BS and removed request for a team July 27, 2026 17:30
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