webdriverio / webdriverio/desktop-mobile
chore(electron): npm deprecate @wdio/electron-cdp-bridge after 10.2.0 ships
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 6
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 33
Description
Follow-up to #340 / #481 — @wdio/electron-service now consumes the shared @wdio/native-cdp-bridge, and @wdio/electron-cdp-bridge has been deleted from the monorepo.
Once @wdio/electron-service@10.2.0 is published stable (after the -next line), deprecate the retired package on npm so existing installs are pointed at the replacement:
npm deprecate @wdio/electron-cdp-bridge "Merged into @wdio/native-cdp-bridge; install @wdio/electron-service@>=10.2.0 (the CDP transport is now an internal implementation detail)."
Notes
- Manual maintainer step — it can't run through the releasekit standing-PR flow, since the package no longer exists in the workspace.
- Gate on the stable 10.2.0 release, not the prerelease, so
-nexttesters aren't stranded. - Already-published versions (last was
@wdio/electron-cdp-bridge@10.1.0) stay on npm; this only adds the deprecation notice.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named because this is a manual npm release step. First verify that @wdio/electron-service@10.2.0 is stable rather than a -next release, then deprecate @wdio/electron-cdp-bridge; it is done when npm shows the deprecation notice pointing users to the replacement.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100