-
Notifications
You must be signed in to change notification settings - Fork 595
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
v7.0.0 #700
Comments
I take the reactions as approval of the changes. I figure I'll let this sit here for a day or so before going ahead with merging everything so that people who have better things to do during the weekend get a chance to review it. |
I think skipping async until someone really wants to champion that feature is fine. These changes look needed. As we spoke via IRC earlier, we should do a beta release before we do a production release on 7.0.0 and make sure everything is working together for a bit before we fully release. |
I second the words of @bcomnes. |
Ohh, I forgot to post here, for those not on IRC. I've been using it for the past week (not in production yet) but it has held up nicely, no issues so far. |
Thanks @tornqvist, change log looks great to me 👍 |
🎉 v7.0.0 has now been published! |
Thank you @tornqvist for your hard work on this! |
We have a few breaking changes queued up for the next major release and I think it's about time to move ahead with those.
Related:
There were discussions in #563 about including asynchronous routes in v7 but the discussion on async routes kind of died off in #653. Also, it could very well be added in a minor later on and is easy enough to implement in user land.
The text was updated successfully, but these errors were encountered: