Skip to content

feat: port upstream service changes (9.28.0 → 9.29.1+) into the extract#40

Merged
kamal-kaur04 merged 1 commit into
migration/monorepo-add-wdio-browserstack-servicefrom
feat/upstream-parity-9.29
Jul 10, 2026
Merged

feat: port upstream service changes (9.28.0 → 9.29.1+) into the extract#40
kamal-kaur04 merged 1 commit into
migration/monorepo-add-wdio-browserstack-servicefrom
feat/upstream-parity-9.29

Conversation

@AakashHotchandani

Copy link
Copy Markdown
Collaborator

Why

The extract was copied from webdriverio/webdriverio at ~9.28.0. The monorepo has since shipped several @wdio/browserstack-service changes (npm latest is now 9.29.1) that are not in this repo. Publishing from here without them would ship an older codebase under a newer version — a regression for users. (PR #39 only synced this repo's own main, which is the old-flat gRPC core — a different source.)

What's ported (net service-src delta, v9.28.0 → upstream main — 20 files, +823/−46)

PR Type
#15335 feat one-to-many Test-Case-ID tagging (setCustomTestCaseId) — new customTags.ts, custom-tags-handler.ts, cli/modules/customTagsModule.ts + service/insights wiring
#15259 feat Load Testing Service (LTS) support (isLoadTestingSession, LTS session id, gRPC/testHub)
#15310 fix finish the correct test/hook on mocha timeout (service.ts, types.ts)
#15331 fix isolate per-batch failures in the request queue
#15379 fix ship a11y Browser type augmentations
#15358 fix upgrade yauzl^3.4.0 (node hang on zip) — lockfile updated minimally (yauzl-only)

Method & validation

  • Per-file 3-way merge (base = upstream v9.28.0, theirs = upstream main, ours = this repo) so upstream changes and this repo's own changes both survive.
  • ✅ The earlier Semgrep fix (new RegExp(...)endsWith/slice in util.ts/insights-handler.ts) is preserved.
  • 0 merge conflicts; npm run build (buf generate + esbuild + tsc) passes (build/index.js 2.6mb).
  • Lockfile change is yauzl-only (^3.0.0^3.4.0, resolved 3.4.0) via --legacy-peer-deps=false to stay CI-consistent.

Notes

🤖 Generated with Claude Code

….28.0 → 9.29.1+)

The extract was copied from webdriverio/webdriverio at ~9.28.0; the monorepo has since
shipped several @wdio/browserstack-service changes not present here. Porting the net
service-src delta (v9.28.0 → official main) so the first publish from this repo doesn't
regress users. Captured PRs:

  - feat #15335  one-to-many Test-Case-ID tagging (setCustomTestCaseId) — new customTags.ts,
                 custom-tags-handler.ts, cli/modules/customTagsModule.ts + service/insights wiring
  - feat #15259  Load Testing Service (LTS) support (isLoadTestingSession, LTS session id, gRPC)
  - fix  #15310  finish the correct test/hook on mocha timeout (service.ts, types.ts)
  - fix  #15331  isolate per-batch failures in the request queue
  - fix  #15379  ship a11y Browser type augmentations
  - fix  #15358  upgrade yauzl -> ^3.4.0 (node hang on zip); lockfile updated minimally

Method: per-file 3-way merge (base = upstream v9.28.0, theirs = upstream main, ours = this
repo), so upstream changes AND this repo's changes both survive. Verified: the earlier
Semgrep fix (regex -> endsWith/slice in util.ts / insights-handler.ts) is preserved, 0 merge
conflicts, and `npm run build` (buf generate + esbuild + tsc) passes.

NOTE: #15316 was not a merged monorepo commit (open PR / different id) — capture on merge.
Dependency-package changes (@wdio/utils #15305 etc.) are separate published packages, not
ported here.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@AakashHotchandani AakashHotchandani requested a review from a team as a code owner July 10, 2026 05:30
@AakashHotchandani AakashHotchandani requested review from 07souravkunda and pranay-v29 and removed request for a team July 10, 2026 05:30
@kamal-kaur04 kamal-kaur04 merged commit a56cd70 into migration/monorepo-add-wdio-browserstack-service Jul 10, 2026
0 of 3 checks passed
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