chore(v8): remove @wdio/browserstack-service (now published by BrowserStack from its own repo) - #15319
Closed
AakashHotchandani wants to merge 1 commit into
Closed
Conversation
…ck from its own repo) v8 line. The BrowserStack WebdriverIO service is now maintained and published by BrowserStack from browserstack/wdio-browserstack-service via npm OIDC trusted publishing, on an independent cadence (per TSC agreement). The 8.x line continues under the `v8` npm dist-tag, published from the new repo's `v8` branch. End users are unaffected: same npm package name `@wdio/browserstack-service`, same `services: ['browserstack']` config. - delete packages/wdio-browserstack-service - drop the workspace reference from tests/typings/setup.js + tests/typings/webdriverio/tsconfig.json types[] - repoint in-repo source links (README bullet removed; CloudServices.md + Multiremote.md -> github.com/browserstack/wdio-browserstack-service) - regenerate package-lock.json (npm workspace lockfile) Kept intentionally (the package stays on npm): the wdio-cli init-wizard entry and the `npm install @wdio/browserstack-service` docs. Note for v8: a wizard install resolves the npm `latest` (9.x) by default; if you'd prefer v8 scaffolds to pin the `v8` dist-tag (or to drop the entry on the v8 line), happy to adjust + update the cli snapshot. The auto-generated /docs/browserstack-service page is built from the package README, so it will no longer be generated after removal — happy to add a redirect or stub, your call. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
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
1 participant
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.
What & why
Removes
packages/wdio-browserstack-servicefrom the v8 line of the monorepo.@wdio/browserstack-serviceis now built and published by BrowserStack from browserstack/wdio-browserstack-service (branchv8→ npm dist-tagv8) via npm OIDC Trusted Publishing — same package name, sameservices: ['browserstack'], zero user-facing change.> 8.48.3on thev8dist-tag) with provenance.v8branch (e.g. fix(wdio-browserstack-service): emit screenshot-on-failure in v8 CLI/… #15330 "emit screenshot-on-failure in v8 CLI"; verify others).packages/wdio-browserstack-servicePRs/releases is in place.Necessary code changes in this PR (checklist)
git rm -r packages/wdio-browserstack-servicev8so the removal covers files added by v8 service PRs merged since.tests/typings/setup.js— drop the'@wdio/browserstack-service': 'packages/wdio-browserstack-service'mapping.tests/typings/webdriverio/tsconfig.json— drop the@wdio/browserstack-serviceentry.package-lock.json.packages/wdio-cli/src/constants.ts(config-wizard entry) andwebsite/docs/**— the package still exists on npm.Companion