-
Notifications
You must be signed in to change notification settings - Fork 176
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
1.3.2 branch #4107
1.3.2 branch #4107
Conversation
r=me for releasing. once released we plan to tag this but not merge it |
The parent commit here is 713c90e |
Wait, no, not r=me, we should include the doc patches |
cherry-picked |
ty. r=me, will start publishing soon (commit ac39015) crates to publish:
|
You should just do Also testdata |
I still don't trust magical tools that publish everything for you, especially if we need to wait with a manual step. Also I wanted to parallelize, which I've been succeeding at. |
Everything except datagen and testdata is released and tagged. @robertbastian what should I do for testdata? |
I guess I just run |
Let's leave this PR open and unmerged and merge a separate PR that contains your 132 commit onto main so that main reflects the correct versions |
The 132 commit conflicts with main |
All published |
4108 |
No description provided.