-
Notifications
You must be signed in to change notification settings - Fork 104
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
New Release #216
Comments
Yo, undead maintainer here again. This project never automated releases and I got real real lazy. I've helped bring some other folks up to speed on the release procedure, but the release process is pretty garbage, and so I understand why they've not be super proactive about it. I was really going to write a script to do this last time I explained it, but I couldn't come up with a quick hack to up the version automatically. I now have the insight that theres not a good reason to want to do this automatically. I built a thing and used it to published 0.5.0 (to reflect the large amount of recent changes). It is available here. I also sent out #217 for review. I actually intended for you to review it, but I guess only whitelisted people can review, so I tagged Damien. EDIT: please feel free to review it as well. |
@acmcarther Thank you!!! Yeah, there's a lot here. #212 is also a big one... I wonder what the release number should be for that one. Regardless, #217 seems awesome and makes me happy as a fan of this project 😄 Thanks for being undead! |
I think once #217 is merged this issue can be closed |
Closing, per #216 (comment) |
What's the process for doing releases for
cargo raze
? I think there's been a bunch of nice changes that have gotten in and would like to be able to use them without cloning and building the project locally. I think it'd be awesome if a release could be made following the merge of #212The text was updated successfully, but these errors were encountered: