-
Notifications
You must be signed in to change notification settings - Fork 472
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
Time for new release? #1923
Comments
Personally I wouldn't say there have been a vast amount of fixes since the last release, although lots of dictionary changes: I've tagged some (non-dictionary) PRs, I'd suggest it might be nice to get in before a release: FWIW, for me at least I run the git version in my CI to pick up the latest typos (and to avoid big bang hits of new additions which need fixing). |
@peternewman I'm inclined to cut a release. We can always do another one quickly after those other PRs are merged |
@larsoner |
There have been a ton of fixes and dictionary changes since the last release; it'd be great to have a new release to take advantage of them.
The text was updated successfully, but these errors were encountered: