Repository navigation
chore(deps): ignore der until cms 0.3.0 ships - #463
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Dependabot opened a bump of
deron its own (0.7 to 0.8). It cannot build:cms 0.2anddpp-sealwould sit on differentders, so the seal path stops compiling.x509-certandconst-oidwere already ignored for the same reason;derbelongs with them.The comment above the ignore list is also brought up to date. The only
cmson the RustCrypto train is a release candidate (0.3.0-rc.0), and it rides stableder,x509-cert,spkiandconst-oid. The note that the newestcmsrides release candidates of those was out of date. The rule itself is unchanged: no release candidate under the seal path, and the whole stack moves in one PR oncecms 0.3.0is published.Comments and one added ignore entry; no code, workflow or lockfile change.