How often a new version will publish?

[Airkro]

It seems done by manual. even a PR merged, we still have to wait for a long time.

Any solutions?

[PKief]

Hi @Airkro thanks for opening this discussion! You're right, every release of this extension is a manual process, which requires effort. I already thought about automating it.

The necessary release steps are:

• Go through all commits since the last "Release x.x.x" commit and create the Changelog.md file
• Update package.json version
• Recreate preview images (already automated via npm script)
• Recreate contributors image (already automated via npm script)
• Publish it on VS Code Marketplace and Open VSX registry

I think it would be nice to find a solution for the creation of the changelog.md file. Then it would be possible to automate the whole release process, which would be really nice and safe my time.🤔

To answer your question: I spend some manual time every two months to release this extension (takes approx. 1-2h, depending on how many changes occurred).

[PKief]

Just to update this discussion: The release process was significantly improved at the beginning of the year and it was fully automated. This means that from now on there will be much more frequent updates and it will cost me less time. However, I don't want to create a new release for every single commit, because it would bring too much network load and it's not really necessary. Nevertheless, I think that the release cycles will become smaller and from now on a release will be made at least once every four weeks. But this is always somewhat dependent on how many changes were actually made and how quickly they should be delivered. But it has become significantly better :)