Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.29%. Comparing base (5b3ef11) to head (25318e6).
⚠️ Report is 2 commits behind head on rel-0.23.

@@            Coverage Diff            @@
##           rel-0.23    #3020   +/-   ##
=========================================
  Coverage     95.29%   95.29%           
=========================================
  Files            97       97           
  Lines         21852    21856    +4     
=========================================
+ Hits          20823    20827    +4     
  Misses         1029     1029           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I believe the failed checks are not caused by my PR, rather pre-existing issues.

I believe the failed checks are not caused by my PR, rather pre-existing issues.

These will be addressed shortly via #3021 -- please rebase.

Need to update the lockfiles in the last commit.

Benchmark results

Instruction counts

Significant differences

There are no significant instruction count differences

Other differences

Wall-time

Significant differences

There are no significant wall-time differences

Other differences

Memory usage

Key:

• ∑: sum usage for entire benchmark run
• 🔝: peak usage
• B: bytes
• a: allocations

Significant differences

There are no significant memory usage differences

Additional information

Historical results

Checkout details:

• Base repo: https://github.com/rustls/rustls.git
• Base branch: rel-0.23 (5b3ef11)
• Candidate repo: https://github.com/TaeHagen/rustls.git
• Candidate branch: rel-0.23 (25318e6)

Thank you. I would appreciate if you could cargo publish sooner rather than later. I'm waiting to depend on the new version in my repo, and would like to avoid hardcoding a commit hash.

Thank you. I would appreciate if you could cargo publish sooner rather than later. I'm waiting to depend on the new version in my repo, and would like to avoid hardcoding a commit hash.

I'll remind you that you're relying on our maintenance for free (and there's currently not much funding); if you want us to care about your organization's needs, I'm happy to pitch you a support contract -- feel free to email me.

I've published 0.23.38.

Unfortunately, we don't have much in the way of a significant amount of funding at this time, and likely don't need ongoing support. However, I would be more than happy to donate. Where is the best place to do that?

However, I would be more than happy to donate. Where is the best place to do that?

Much appreciated!

Right now, we only have the maintainers' GitHub Sponsors pages listed on the main repo page. Does that work for you?

It does, however, it is annoying because I have to sponsor each member individually. But I suppose that's fine, I'll do that now.