Merged
Conversation
sbihel
approved these changes
Feb 3, 2026
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
2 participants
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.
Description
We have an issue since version 0.12, because of
ssi-core.ssi-coreis set to version 0.2.2 inssi, but there is a version 0.2.3 released out there.ssi-core0.2.3 introduces a breaking change compared to 0.2.2. So it should have beenssi-core0.3.Because of 2., cargo has trouble selecting the correct version of
ssi-core, and because of 1. this is triggering errors.So this PR solves this issue by bumping
ssi-coreto 0.3.0. Of course we also need to bumpssi.I wrote a custom tool to automatically bump versions (I may release it at some point), so we don't have to manually figure out what needs bumping in the future. It can tell what dependents need bumping, release stuff that needs releasing in the correct order, and generate tags.