Optionally support deploying to OpenVSX about semantic-release-vsce

[felipecrs]

It was part of the original implementation until I realized that it didn't work.

semantic-release-vsce/lib/publish.js

Lines 39 to 43 in 5b40b1b

	const ovsxUrl = `https://open-vsx.org/extension/${publisher}/${name}/${version}`;
	const ovsxRelease = {
	name: 'Open VSX Registry',
	url: ovsxUrl
	};

[GitMensch]

Please try to don't decouple - one version is better and two entries in the issue messages and releases would be bad, too [maybe a potential second CI could edit the work of the former, but that seems to be a strange design]. For now: whichever release was done first should get the entry (in case only open-vsx is used); more discussion on this can go on in semantic-release/semantic-release#2123.

... thinking of this, maybe it is a good time already to rename this repo (or package.json entries) to something like "semantic-release-vsix-publish", just an idea so far...

Not sure, but do you already use osvx to publish to both marketplaces when it is configured? This may/may not help with the multiple return paths a bit.

[github-actions]

🎉 This issue has been resolved in version 3.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[GitMensch]

Can the message of the bot include the related Open-VSX page in the "the release is available on" message (issue update) shown below and the "this release is also available on" (GH release), too?

[felipecrs]

@GitMensch unfortunately, it's not currently possible: semantic-release/semantic-release#2123

Unless I decouple the ovsx from the semantic-release-vsce, and create a semantic-release-ovsx.