Skip to content

Conversation

@cgwalters
Copy link
Collaborator

Now we can use a proper Digest type.

@cgwalters
Copy link
Collaborator Author

CI here can't succeed on semver-incompat bumps, though what I could do is prep the PR for ostree-rs-ext in advance, and point CI at it temporarily

@jeckersb
Copy link
Collaborator

CI here can't succeed on semver-incompat bumps, though what I could do is prep the PR for ostree-rs-ext in advance, and point CI at it temporarily

Yeah I was just looking into that. Wrapping my head around the dependency graph of things in CI. I started on porting ostree-rs-ext over to ocidir 0.3.0 which if I'm following is required to untangle all of this.

@cgwalters

This comment was marked as outdated.

@cgwalters cgwalters force-pushed the bump-oci-spec branch 3 times, most recently from 24d06d5 to e36dc5f Compare September 18, 2024 21:07
Now we can use a proper Digest type.

Signed-off-by: Colin Walters <walters@verbum.org>
@cgwalters
Copy link
Collaborator Author

@jeckersb this is ready now, I pointed CI at your branch in ostreedev/ostree-rs-ext#663

Then we can release this crate and change your PR to use the published crate, then when we publish ostree-rs-ext we can change this to reference the published version of that...

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.

2 participants