-
Notifications
You must be signed in to change notification settings - Fork 9
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
v2.3.1 #300
v2.3.1 #300
Conversation
Tag has been pushed. 2.3.1 should be published in a few minutes. |
Thanks for the lightning fast action @zachmullen 😁 |
@scottwittenburg @zachmullen 2.3 was an unintended release, and I was planning to scrub it from NPM pending a discussion. The changes introduced in #293 are significant enough to require a major version update, so I was going to suggest moving to 3.0.0 after #297 gets resolved, which I haven't had time to fix. Do you need the changes introduced in 2.3.0 (ts, import restructure)? We can certainly keep going with 2.3, but it would somewhat contradict semver guidelines. |
I see, the point was to release the changes from #299. @scottwittenburg you should know that upgrading to 2.3 will break your project. This library hasn't had so much traffic that it has been necessary to maintain a "stable" branch and a "next" branch to allow us to push minor patches like #299 while working on larger changes. Apologies for the confusion. Let me know what you want do now. |
I don't have a strong preference. |
@subdavis We're currently on Other than that, I don't have any preference which path you take. But when you decide what you're going to do, I'll get in touch about the path forward for my application. Thanks! |
Unless someone has a better suggestion, I'm going to
|
That would be great, thanks! |
No description provided.