Prepare 0.23

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "hyper-rustls"
-version = "0.22.1"
+version = "0.23.0"
 edition = "2018"
 authors = ["Joseph Birr-Pixton <[email protected]>"]
 license = "Apache-2.0/ISC/MIT"

README.md

@@ -8,6 +8,10 @@ and the [hyper HTTP library](https://github.com/hyperium/hyper).
 [![Documentation](https://docs.rs/hyper-rustls/badge.svg)](https://docs.rs/hyper-rustls/)
 
 # Release history
+- 0.23.0 (2021-11-16):
+  * Upgrade to rustls 0.20. Thanks to @g2p.
+  * Add new HttpsConnectorBuilder API. Thanks to @g2p.
+  * Add the tls12, logging, http1 and http2 features. Thanks to @g2p and @marwes.
 - 0.22.1 (2020-12-27):
   * Fixing docs.rs build; no other changes.
 - 0.22.0 (2020-12-26):
@@ -41,4 +45,3 @@ hyper-rustls is distributed under the following three licenses:
 These are included as LICENSE-APACHE, LICENSE-MIT and LICENSE-ISC
 respectively.  You may use this software under the terms of any
 of these licenses, at your option.
-

RELEASING.md

@@ -0,0 +1,26 @@
+# Making a hyper-rustls release
+
+This is a checklist for steps to make before/after making a rustls release.
+
+1. Attend to the README.md: this appears on crates.io for the release, and can't be edited after
+   the fact.
+   - Ensure the version has a good set of release notes.  Move old release notes to OLDCHANGES.md
+     if this is getting excessively long.
+   - Write the version and date of the release.
+2. Run `cargo update` followed by `cargo outdated`, to check if we have any
+   dependency updates which are not already automatically taken by their semver specs.
+   - If we do, take them if possible with separate commits (but there should've been
+     dependabot PRs submitted for these already.)
+3. Now run `cargo test --all-features` to ensure our tests continue to pass with the
+   updated dependencies.
+4. Update `Cargo.toml` to set the correct version.
+5. Make a commit with the above changes, something like 'Prepare $VERSION'.  This
+   should not contain functional changes: just versions numbers, and markdown changes.
+6. Do a dry run: check `cargo publish --dry-run`
+7. Push the above commit.  Wait for CI to confirm it as green.
+   - Any red _should_ naturally block the release.
+   - If rustc nightly is broken, this _may_ be acceptable if the reason is understood
+     and does not point to a defect.
+8. Tag the released version: `git tag -m '0.20.0' v/0.20.0`
+9. Push the tag: `git push --tags`
+10. Do the release: `cargo publish`.