cursorless-dev
Separate VSCode publish jobs
Implements the suggestion from #3104 to separate the publish jobs.
- Split VSCode publish into two separate jobs (Open VSX and VS Marketplace)
- Ensures the same VSIX file is published to both registries
- Build and Open VSX publish happen together, VS Marketplace publishes sequentially to the same VSIX
- Allows independent reruns of each marketplace publish job
- Removed skipDuplicate as it's no longer needed with separate jobs
Amp-Thread-ID: https://ampcode.com/threads/T-c5112243-7633-492f-911d-5c3e5998c847
I wouldn't say I'm against go in this direction. At the same time is it really that problematic to rebuild the binary in case the vscode market plays publishing doesn't work? We're already rebuilding the binary between testing and publishing. I think the best solution would be to build the binary once and then reuse it for testing and publishing, and if we're not going to do that the current set up is fine. How do you feel?
If we're going this direction I think I'd opt for 3 steps: build, publish openvsix, and publish vscode. The latter two can run in parallel and both depend on build. Ideally one marketplace being down shouldn't block the other, and we should be able to rerun either.
