Skip to content

Fix versioning semantics and update/fix CHANGELOG #242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gnikit opened this issue Jun 30, 2021 · 3 comments · Fixed by #244
Closed

Fix versioning semantics and update/fix CHANGELOG #242

gnikit opened this issue Jun 30, 2021 · 3 comments · Fixed by #244
Assignees

Comments

@gnikit
Copy link
Member

gnikit commented Jun 30, 2021

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).

  1. The changelog also needs to be updated to refer to these releases. At least the ones that are published on GitHub.
  2. release v2.2.0 also needs a fix; drop the debugging commit and make that a new release of its own v2.2.1.
  3. Then make a release for v2.2.2 which is the version currently on VS Code marketplace.
  4. Keep the rest of the commits for version v2.3.0 or something
@gnikit
Copy link
Member Author

gnikit commented Jun 30, 2021

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.

@gnikit
Copy link
Member Author

gnikit commented Jun 30, 2021

use

GIT_COMMITTER_DATE="$(git show --format=%aD | head -1)" git tag -a v2.0.0 -m 2.0.0

to backdate the new tags

@gnikit
Copy link
Member Author

gnikit commented Jun 30, 2021

versions done

2.0.0
2.0.2
2.1.0

@gnikit gnikit linked a pull request Sep 18, 2021 that will close this issue
19 tasks
@gnikit gnikit mentioned this issue Sep 18, 2021
19 tasks
@gnikit gnikit self-assigned this Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant