Version confusion between GH sources and vscode Marketplace

[mthierba]

The vscode Marketplace currently offers version 2.3.0 of the extension:

The GitHub repo, however, has 2.1.1 as the latest release:

New commits were made to main after the latest GH release, though:

I'm assuming there is some manual process at work here. Can something be done to keep both views of the project in sync?

[gbrueckl]

hey @mthierba, you are absolutely right, there is definitely a mismatch as i am quite lazy to do both releases at the same time I will try to at least also create releases on Github for minor versions and tag them accordingly

[mthierba]

I could help setting up a deployment pipeline if you'd like? Was just wondering whether there were any other reasons.

[gbrueckl]

sure, I would really appreciate it

So I guess the gitHub repo would be the master and whenever a new release is created, a could trigger a github action to also publish the final VSIX to the VSCode gallery, right?

[mthierba]

There are two options:

1. Trigger on Release

• Assumes release is created manually
• publish vsix
• easier, but more manual steps

2. Trigger on Tag

• Create GitHub release from tag
• build and publish vsix from release

Both options are safe in that they require an explicit trigger, i.e. it's not "CD", just "CI".

[gbrueckl]

a Release also always generates a Tag, no? I would probably do it "On Release" so its obvious when a new version also has to be published to the VSCode gallery I already found some good examples for this, now I just need some time to implement it

[gbrueckl]

finally implemented this :D