Update service for WDIO v9

[goosewobbler]

WDIO v9 is coming along nicely, there is a bit of work to do in the service around this, since we are dropping Node 16 I think we cut a major version and punt the IPC bridge replacement to v8.

Tasks:

• [x] Code updates
• [x] Publish pre-release builds
• [ ] Update docs for new release workflows
• [ ] Manual test with wdio-electron-service-example
• [ ] Manual test with electron-boilerplate (can use the v9 branch)
• [ ] Update WDIO peerdep range to ">9.0.0" (after the WDIO v9 release)
• [ ] Update WDIO deps to "^9.0.0" (after the WDIO v9 release)
• [ ] Publish full release
• [x] Ensure version is updated in the package correctly after release

https://github.com/webdriverio/webdriverio/issues/10362

[seanpoulter]

Is the plan to make a v8 branch and keep v9 development on main?

[goosewobbler]

Yes, I'd have the WDIO v9 version on main which corresponds to v7 of the service. I'd probably name the legacy version branch wdio-v8 or v6 to avoid confusion as the service major versions don't match the WDIO ones. I'm not planning on backporting anything at the moment, but it could be useful to keep around. I don't think WDIO v9 will affect the service anywhere near as much as previous major versions did.

[goosewobbler]

I created the wdio-v8 branch in case we need to backport anything to 6.x.

main will require WDIO v9 when #443 and #666 are merged, and will be released as v7.

[goosewobbler]

Re-opened to keep track of the remaining tasks for the release.

[goosewobbler]

@christian-bromann I need to publish the dependent packages to get the pre-releases for the service working, I was considering to publish them as @wdio-electron/types and @wdio-electron/utils for which we need the @wdio-electron org; I was going to create this org but thought I'd check first, maybe you should create it and I can join.

Or perhaps publishing them under the main org as @wdio/electron-types and @wdio/electron-utils is better?

[christian-bromann]

Or perhaps publishing them under the main org as @wdio/electron-types and @wdio/electron-utils is better?

Yes, no need to create another org, let's use @wdio/ to which you can publish to through the bot.

[goosewobbler]

Finally got a working pre-release in 7.0.0-beta.9. Tested in wdio-electron-service-example.

[goosewobbler]

electron-boilerplate is still broken on v9 branch, I'll release anyway as the service works in wdio-electron-service-example.

[christian-bromann]

Let me take a look at the boilerplate, I will ping you if I don't know what is going on.

[christian-bromann]

It seems like 7.0.0-beta.11 didn't get pushed to NPM 🤔 However I got the boilerplate working with 7.0.0-beta.10 (there was a bug in Stencil that I fixed but which hasn't been released yet, so reverting that version to v4.18.3 fixed the build).

[goosewobbler]

There's still something up with the release and pre-release workflows, maybe the dry run is creating tags for some reason...

https://github.com/webdriverio-community/wdio-electron-service/actions/runs/10463303622/job/28975088177 https://github.com/webdriverio-community/wdio-electron-service/actions/runs/10462686326/job/28973369345

[goosewobbler]

Reverted to beta.11 and deleted the unused 7.0.0 tag on github, this time I went straight for the full release instead of a dry run followed by full release, it just attempted to release beta.11 again (instead of 7.0.0) 🤔

https://github.com/webdriverio-community/wdio-electron-service/actions/runs/10463968883/job/28976808705

[goosewobbler]

Reopening until we get the full release done, I think we're missing some steps from the release-it monorepo recipe:

https://github.com/release-it/release-it/blob/main/docs/recipes/monorepo.md

[goosewobbler]

Release is done, just need to update electron-boilerplate.

Raised https://github.com/webdriverio/electron-boilerplate/pull/224