You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is mostly a reminder to fix the versioning semantics.
Some of the last few releases do not have the prefix v which is not that big of a deal but it makes it annoying to have to search through tags (not that most people should be doing that anyway).
The changelog also needs to be updated to refer to these releases. At least the ones that are published on GitHub.
release v2.2.0 also needs a fix; drop the debugging commit and make that a new release of its own v2.2.1.
Then make a release for v2.2.2 which is the version currently on VS Code marketplace.
Keep the rest of the commits for version v2.3.0 or something
The text was updated successfully, but these errors were encountered:
I am not sure if there is a way to edit the existing GitHub releases and assign new tags at them, without messing up the order that they are listed, so it might get a bit intrusive. Hopefully only the top 4 releases are really the problem so by the end of it all should be back in the correct chronological order.
This issue is mostly a reminder to fix the versioning semantics.
Some of the last few releases do not have the prefix
v
which is not that big of a deal but it makes it annoying to have to search through tags (not that most people should be doing that anyway).The text was updated successfully, but these errors were encountered: