-
Notifications
You must be signed in to change notification settings - Fork 668
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
Request: cut new release & publish to npm #1783
Comments
Hi! Are you waiting for a specific PR/commit? Not much has happened since 1.1.2, but we could issue a new one if needed 👍 |
just published v1.1.3 :) |
I'll go ahead and close this issue! Thank you for the ping (and for the PR)! |
@afontcu Awesome, thank YOU. Keep up the good work! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Description
Can a release (e.g. 1.1.3) be published to npm?
Problem
Last stable release (1.1.2) is from December
Thank you!
The text was updated successfully, but these errors were encountered: