Is someone interested in preparing the next release? I'm up for doing this if no one else willing to take this up.
I am interested. But don't know about the process. any documentation?
@hramezani cool! Here is the guideline. It's a little outdated since we can't push to the master without an approvement, but we can push via PR. This is the latest reference: #936.
Also, would be nice to merge #997 and #1004 before the release.
I've updated the guideline, see #1006.
@atugushev milestone 4.3.0 is complete now.
Should we wait for #1004 for release?
@hramezani I've merged the #1004. So nothing blocks the release now.
@hramezani CI is green a3e18bd63bf555b78c06fc0356f7d3c6b923fd28, so you can draft a new release.
@atugushev, Thanks for your help. Here is the releases 4.3.0.
@hramezani pip-tools v4.3.0 is approved and released! The milestone could be closed.
Let's keep the issue pinned for a while in case some users have any issues with the release.
Huge thanks to @hramezani for managing this release! 馃帀 馃帀 馃帀
One week without issues. Smooth release. Thanks to everyone involved! I'll close and unpin it.
Most helpful comment
Huge thanks to @hramezani for managing this release! 馃帀 馃帀 馃帀