-
Notifications
You must be signed in to change notification settings - Fork 167
New release? #177
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
Comments
Yep! Planning on cutting a release once #172 and #167 are merged. That being said, both have kinda stalled for unrelated reasons, so I might cut a release on current HEAD in the next couple days. I'll leave this open until that's done :) Good point on adding myself to the README. I'll do that shortly |
@DonnieWest You are my savior |
I would also love to see a new release, do you think there's something I or another interested person could do to help get you there? |
0.5.0 published |
Err, 0.5.1 because of local env silliness. Apologies |
Thank you so much, and fantastic job! |
Thanks for taking over maintainership, @DonnieWest! I see there have been a number of commits over the past few months but no new release tag here or version on npm. Do you have plans for that, or should I start building it myself from master?
By the way, you might want to add yourself as the maintainer in the readme since it's out of date.
The text was updated successfully, but these errors were encountered: