Publish process

[sumneko]

• Auto release (feat(ci): publish platform specific binaries #850 )
• Remove <platform> folder
• All in One
• Publish to VSCode by workflow
• Publish to VSCode according to the platform

[sumneko]

@numToStr Could you please help me to implement Remove <platform> folder and All in One ?

[numToStr]

@numToStr Could you please help me to implement Remove <platform> folder and All in One ?

Sure. I'll update the workflow to build an all-in-one package until we'll be able release platform-specific vsix.

Meanwhile you can remove the platform folder as it won't effect the current workflow.

[sumneko]

We do not need All in One, I could just publish according to the platform, it is not difficault.

[numToStr]

Indeed, that'll be great. We could also setup action to publish platform-specific vsix. It'll cover all the points you've mentioned in the op.

[sumneko]

Oh no, I forgot open-vsx.org , it seems not supports platform-specific vsix .

[sumneko]

See eclipse/openvsx#336 .
We still need the All in One, or we just not release to the market until it supports platform-specific vsix.

[numToStr]

We still need the All in One, or we just not release to the market until it supports platform-specific vsix.

An all-in-one asset is still possible even If you've removed the platform folder. As the workflow already has linux, darwin, and windows marker.

We can remove the all-in-one asset once open-vsx starts supporting platform-specific extensions.

[numToStr]

@sumneko is linux-64 build for arm64 or x86_64?

[sumneko]

I request off-site support @actboy168

[actboy168]

@numToStr linux-x64 means x86_64.

[sumneko]

Done