Skip to content

Use latest cargo-hyperlight in release workflow#1441

Merged
jprendes merged 1 commit intohyperlight-dev:mainfrom
jprendes:fix-release
May 6, 2026
Merged

Use latest cargo-hyperlight in release workflow#1441
jprendes merged 1 commit intohyperlight-dev:mainfrom
jprendes:fix-release

Conversation

@jprendes
Copy link
Copy Markdown
Contributor

@jprendes jprendes commented May 6, 2026

To generate the header's tar and the lib tar, we use cargo-hyperlight.
With the libc changes we need to make sure we use the latest cargo-hyperlight.

Signed-off-by: Jorge Prendes <jorge.prendes@gmail.com>
Copy link
Copy Markdown
Contributor

@ludfjig ludfjig left a comment

Choose a reason for hiding this comment

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

What about just ensure-cargo-hyperlight or modifying it to update version?

@jprendes
Copy link
Copy Markdown
Contributor Author

jprendes commented May 6, 2026

I think we should have a better way of updating this in the base image, the base image currently ships with an ancient version of cargo-hyperlight.
I'll keep it as is now since we have the exact same pattern in a few different workflows, and will make it easier to find-and-replace.

@jprendes jprendes enabled auto-merge (squash) May 6, 2026 22:27
@jprendes jprendes merged commit 1fba3a5 into hyperlight-dev:main May 6, 2026
40 of 41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/bugfix For PRs that fix bugs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants