Internal stuff
– tslint fixes, fix for generated minichangelog, update extension related files
– Automated github release and marketplace publish pipeline
This will allow us to trigger a release build, which will add a github release and marketplace upload immediately after succes.
Happy testing and feedback welcome as usual.
I would like to add a new release before Fosdem in the first weekend of February.
sorry for stupid question but how do I go about getting this working with vscode? I’ve downloaded the files and I see a .vsix file
hold on
I’m going to answer my own stupid question for the benefit of the community
I have installed from vsix dozens of times. Maybe that’s the reason for not explaining this.
But I wanted to prepare a “hey here’s a new beta” post as snippet for my own usage anyway. So it should be no problem to just add your posted link for upcoming betas with the announcement.
When this uhh normal marketplace release happens, might I expect a prompt in VSCode to allow update of the extension? Is there anything I need to allow for my installation to check for this?
I am not sure about installations that have been made via file by the beta testers.
For users of the existing marketplace extension it should at least get displayed as an available update from the extension tab.
But I think I have also seen some kind of prompt for other extensions in the past.
I will install the beta an test it myself.
Anyways I will of course add a post here or maybe some announcement thread in the category to inform more people about the possibility to Check for updates.
