This is technically a breaking change, although probably an OK one.

You'll need to update the import gating accordingly, however, since the tests are now failing.

(whoops sorry, didn't mean to close it)

@tarcieri Thanks, I've fixed the error and I believe this PR does not include any breaking change, since

• no feature is removed
• no API change under cfg

Sorry that somehow I did not receive any notification for your reply.

I've also run cargo semver-checks check-release and it confirms that this PR does not include any breaking change.

@tarcieri All checks have passed, this PR is ready for another review.

@NobodyXu the breaking change would be features being implicitly enabled before and not any longer. That's not going to be caught by a tool like cargo semver-checks.

But it's minor enough it's probably a non-issue.

@NobodyXu the breaking change would be features being implicitly enabled before and not any longer. That's not going to be caught by a tool like cargo semver-checks.

But it's minor enough it's probably a non-issue.

Yeah you are right, I kind of ignore that because I thought it was wrong to enable pkcs8 in feature alloc.
In fact that was one of the motivation for this PR since this bumps the msrv to 1.65.0 in sccache mozilla/sccache#1742

@tarcieri Can you make a new release for pkcs1?