-
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
Request for new release #304
Comments
The PR linked in this issue has been merged and I feel the changes I made to the repo should be in a decent spot for a release. That said though, I've opened up #319 which I feel really completes the UX for cargo workspace support and it'd be nice to have that be the first user experience |
@acmcarther Up to you though. I would otherwise have 3 PRs (including #319) I'd like to get through for a release. #319 being the largest of the 3. |
@acmcarther Actually, I think a release now would be best since it'd unblock some efforts in rules_rust. |
Edit: Done |
Thank you! |
Gonna close this for now to make it cleaner as to what went into this. I'll open a new request when I think a new release is ready. |
Generated by running ```bash LANG=C sed -i '' -e 's/io_bazel_rules_rust/rules_rust/' $(find . -type f -not -path "./.git/*") ``` There's some small amount of sorting in here as well (based on the new name) Closes #499 Blocked by google/cargo-raze#298 and google/cargo-raze#304
I think given recent changes a new release should be made. However, I'd really like it if the release could be made after #303 is merged. Additionally, there are a few PRs before it and there are some other PRs in work that might be worth including as well. But that's up to the code owners (obviously) 😄
The text was updated successfully, but these errors were encountered: