-
Notifications
You must be signed in to change notification settings - Fork 313
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
prepare v0.12.0 release #802
Conversation
And after a quick search, an helpful |
34644ca
to
09b124a
Compare
I dived into
Usage: Aliases v2: any github repo ; use more precise date with
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. Looks good to me.
@jswrenn There is |
Whoops, I thought we deleted that. |
There is no point in running CI only for markdown changes. Such as rust-itertools#802 (prepare releases) and rust-itertools#767 (Contributing.md) https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore
There is no point in running CI only for markdown changes. Such as #802 (prepare releases) and #767 (Contributing.md) https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore
UPDATE: Changelog complete!
Still need to write changelog.Is there any way to easily get all PRs merged after a date/tag? Running this:Only turned up merge commits for:
try_len
method #723LazyBuffer
#727Powerset
count #735Permutations::size_hint
#739But we have plenty more PRs that were merged without merge commits: https://github.com/rust-itertools/itertools/milestone/5?closed=1
I'm quite tempted to adopt a squash-before-merging approach before our next release to simplify this (so we could just list off all commits without too much noise).