Skip to content
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

Versioning #8

Open
func0der opened this issue Jul 9, 2024 · 0 comments
Open

Versioning #8

func0der opened this issue Jul 9, 2024 · 0 comments

Comments

@func0der
Copy link

func0der commented Jul 9, 2024

Hey there,

thanks for your work.

I wanted to quickly make a suggestion to keep a CHANGELOG.md as other projects do, tag your releases, use github releases or any similar kind of conveying, what your versions are.
Additional it would help if there would be notes on the releases. I have a old 1.x version here and see that the new version is 3.x.

I now am stuck either updating and 'trusting' that my way of using the library is not broken in v3 or I dig through all the code and guess which version of the code is actually published on NPM.

I understand that this is addtional work, but afaik there are some ways of automating that process:

Keep up the great work :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant