Skip to content

packages: update mirage-crypto to 2.0.1 #731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 10, 2025
Merged

Conversation

psafont
Copy link
Member

@psafont psafont commented Jun 3, 2025

BREAKING: replaces cstructs for strings, and changes rng generators' API.

Because they are breaking changes, it means, we can't have clean CI in this repository, instead I've tested a full xenserver build with the changes. No issues were found (SR 218740)

matching xapi branch is at xapi-project/xen-api@master...psafont:xen-api:private/paus/stringy-crypto

Bengang is planning on doing a release on Friday, will open both PRs then.

BREAKING: replaces cstructs for strings, and changes rng generators' API

Signed-off-by: Pau Ruiz Safont <[email protected]>
@psafont psafont force-pushed the private/paus/stringy-crypto branch from 287c506 to 2c2d06c Compare June 3, 2025 11:17
@lindig
Copy link
Collaborator

lindig commented Jun 4, 2025

What does it mean to replace ctruct with strings? The crypto package drops its cstruct dependency? But we have other packages that still use cstruct?

@psafont
Copy link
Member Author

psafont commented Jun 4, 2025

What does it mean to replace ctruct with strings?

In the context of the package it means cstructs are removed from the dependency, and its API now uses strings instead. This does not mean that the cstruct package is removed from the repository because it has a large use-base.

@psafont psafont marked this pull request as ready for review June 9, 2025 09:13
@psafont psafont merged commit 4f4212f into master Jun 10, 2025
1 of 3 checks passed
@psafont psafont deleted the private/paus/stringy-crypto branch June 10, 2025 13:37
github-merge-queue bot pushed a commit to xapi-project/xen-api that referenced this pull request Jun 10, 2025
Unfortunately mirage-crypto has accumulated breaking changes:
- Cstructs have been replaced with strings
- The digestif library has replaced ad-hoc hash implementation

A deprecation has happened as well:
- RNG initialization has changed

Because there are breaking changes, xs-opam changes need to be
introduced at the same time:
xapi-project/xs-opam#731

Only xapi is affected by the breaking builds, so no other toolstack
repositories have incoming PRs.
I've tested builds with  Smoke and validation tests: SR 218740

This means that the merge will be done as such:
- Both PRs are approved
- First I will merge xs-opam will be emrged (with failing CI)
- Then this PR will be merged with the merge train that runs tests
before actually merging.
- CI is rerun manually on xs-opam to make it green again

After merging both xenserver's CI should create a successful build with
both PR included
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants