Skip to content

Generate a CoRIM#2558

Open
labbott wants to merge 2 commits into
masterfrom
dev_corim
Open

Generate a CoRIM#2558
labbott wants to merge 2 commits into
masterfrom
dev_corim

Conversation

@labbott

@labbott labbott commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

labbott added 2 commits June 10, 2026 15:28
This is a dependency for some other work
When making a build to test it's useful to have a pre-generated
CoRIM file. Generate one for each build. RoT builds will have
two entries.
@labbott labbott requested review from cbiffle and flihp as code owners June 10, 2026 19:54
Comment thread build/xtask/src/dist.rs
caboose_args
.version_override
.clone()
.unwrap_or("0.0.0-testing".to_string()),

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any benefit to using the git revision here?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could, this is also designed to be used as a placeholder so 🤷

@mkeeter

mkeeter commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

From pedantically browsing the lockfile changes, there are a few upstream crates that we could update to minimize the number of different versions in the dependency tree:

  • attest-data in dice-util is still on the older sha3
  • rats-corim is on an old version of strum; we may also want to reorganize so that clap isn't in the library crate's dependency tree

(this shouldn't block the PR, obviously)

@labbott

labbott commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator Author
* `attest-data` in `dice-util` is still on the older `sha3`

I spotted that too and was going to take a pass at that after I got a few more things done

* `rats-corim` is on an old version of `strum`; we may also want to reorganize so that `clap` isn't in the library crate's dependency tree

Ah good point. That repo needs some restructuring.

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