Cargo: 0.17.0 -> 0.18.0, update cc, data-encoding, oid-registry #183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cargo: 0.17.0 -> 0.18.0
This commit updates the version number to reflect that a breaking change was made in
master
. This in turn fixes thecargo-semver-checks-action
finding in CI.In ce50cdb a new variant (
GeneralName:Invalid
) was added toGeneralName
, and since that enum isn't markednon_exhaustive
, this is a semver incompatible change that necessitates increasing the Cargo version.This was correctly flagged by the CI
cargo-semver-checks
action, but since the commit was pushed directly tomaster
it seems to have been overlooked.@chifflier would you be open to switching to a pull request workflow? I would be available to try and review incoming PRs if you're interested in that, but even if you merge them yourself without review I think it's worthwhile as a way to verify CI passes pre-merge.
Cargo: update cc, data-encoding, oid-registry
Updates 3 packages to latest compatible versions:
Updating cc v1.2.11 -> v1.2.13
Updating data-encoding v2.7.0 -> v2.8.0
Updating oid-registry v0.8.0 -> v0.8.1
Notably the oid-registry update requires replacing usages of the deprecated typo'd
OID_X509_EXT_INHIBITANT_ANY_POLICY
OID withOID_X509_EXT_INHIBIT_ANY_POLICY
.Replaces #181, #182 where I noticed the builds failling.