Skip to content
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

chore: Update container version to g538dba3 #178

Merged

Conversation

RuoqingHe
Copy link
Contributor

@RuoqingHe RuoqingHe commented Feb 18, 2025

Summary of the PR

We have switched to git sha1 tagging since v49. For details, see:
rust-vmm/rust-vmm-container#121.

Requirements

Before submitting your PR, please make sure you addressed the following
requirements:

  • All commits in this PR have Signed-Off-By trailers (with
    git commit -s), and the commit message has max 60 characters for the
    summary and max 75 characters for each description line.
  • All added/changed functionality has a corresponding unit/integration
    test.
  • All added/changed public-facing functionality has entries in the "Upcoming
    Release" section of CHANGELOG.md (if no such section exists, please create one).
  • Any newly added unsafe code is properly documented.

@RuoqingHe
Copy link
Contributor Author

Awaits rustvmm/dev:g538dba3 to be published to our dockerhub.

We have switched to git sha1 tagging since v49. For details, see:
rust-vmm/rust-vmm-container#121.

Signed-off-by: Ruoqing He <[email protected]>
@RuoqingHe RuoqingHe force-pushed the update-containers-to-g538dba3 branch from 97af4f5 to 6bd7e4d Compare February 18, 2025 14:41
@roypat
Copy link
Collaborator

roypat commented Feb 18, 2025

This supercedes #175 as well (just putting this here so we don't forget to close that one as well after merging this)

@stefano-garzarella stefano-garzarella merged commit 2d733b0 into rust-vmm:main Feb 18, 2025
3 checks passed
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