0.13.0 release planning
sigoden opened this issue · comments
There are two updates that are very important to me, I hope to see the new release soon.
- Use
ring@0.17.rcgen@0.12.1still has a dependency onring@0.16
ring v0.16.20
└── x509-parser v0.15.1
└── rcgen v0.12.1
- RSA support
Thank you all.
FTR the way x509-parser 0.15.1 depends on old ring is through a direct dependency, not because it depends on rcgen. That would be a circular dependency which Cargo doesn't allow (outside of dev dependencies but this isn't the case here).
I think it would be great to release -- I think it would be nice to get #233 and #223 in, though.
I agree, IMO it's a good moment to release, we've had multiple larger changes and fully moving to newest ring is a good motivation.
Maybe we can do some renaming in advance of #242 so that #242 will be non-breaking?
I'm supportive of the idea but I'm not sure I know what you have in mind. #242 doesn't seem to change any existing fns, but introduces new ones (KeyPair::from_pem_and_sign_algo_with_more_formats, KeyPair::from_der_and_sign_algo_with_more_formats). It doesn't seem breaking to me, or I'm overlooking where some staged renaming will help.
I didn't like those APIs so there is a different proposal in the comments.
I didn't like those APIs so there is a different proposal in the comments.
Aha! Thanks, I understand the proposal now.
I think we're ready to prepare a release now? 🤞 It looks like #250 could be handled in a follow-up point release w/o semver complication.
I think we'd like to get #252 in, but after that I guess we're ready.
rcgen 0.13 was published this morning, and uses x509-parser 0.16.