Release 0.11

[Jakuje]

The PKCS#11 3.2 changes as well as most of the important mechanisms landed. Is there anything else than #318, #317 that we need before cutting next release?

Any thoughts about #290 (API change) and #302 (could land later as it wont change API)? Any other ideas/thoughs @hug-dev @wiktor-k ?

[wiktor-k]

FWIW I'd like to proceed with #290 but we can release 0.11 and then the next release will be a bit breaking. There's no pressure on my side but I think #290 addresses some common concerns...

[hug-dev]

Agree that we can have #290 merged before releasing! For me it's good as it is :)

[wiktor-k]

Ack. Thanks for the encouraging words, I'll take a stab at updating that one ASAP! 🙇

[hug-dev]

Maybe #289 as well since it addresses bugs? We could split the PR ourselves and mention @mematthias as original author if they don't have the time/will to do the work themselves :)

I am generally wary of "scaring away" new contributors with too many comments/change requests 😅 So maybe this one should be on us! Happy to do it.

[Jakuje]

I think most of the 289 is already merged. I just needed a rebase to figure out whats left, but it was not done for months.

[wiktor-k]

Agreed that #289 is merged. I think the only left parts are dependency upgrades (which could be done manually with cargo upgrade --incompatible && cargo update and seeing if that works). The core of #289 was removing bad use of MaybeUninit and that's done.