-
Notifications
You must be signed in to change notification settings - Fork 228
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
Publish beta1 to crates.io #226
Comments
Sure, that can be done. But it wouldn't be a release candidate since it's not ready for release. Also, would like to get #224 merged before doing so |
Thats great! Thanks! |
Hey @TheDan64! Do you have an indication on when you might publish the beta? |
Trying to get #221 fixed and merged first since it's really close to being done. Hopefully this weekend or next. Can't give an exact date but relatively soon |
Didn't get to fixing the aforementioned PR unfortunately but I've gone ahead and published a new version for you: |
Thanks for publishing, I appreciate it a lot! I've run into a small issue though, the release contains a file called
Any idea what that file is? |
No clue. Ugh. Gonna try and re-publish |
|
Thanks! That did fix it. :) |
I'd like to suggest that |
Good idea. Done. |
Is your feature request related to a problem? Please describe.
For Mun, we would really like to make another release based on the latest inkwell version. However, we would really like to use some of the features that have recently landed.
Describe the solution you'd like
It would be great if you could cut another (release candidate) release.
Describe possible drawbacks to your solution
I understand that this is not ideal but it looks like v0.1.0 is still quite far away.
Describe alternatives you've considered
An alternative would be to fork the repository and publish that ourselves but that seems very far from ideal. I really don't want to do that.
The text was updated successfully, but these errors were encountered: