Skip to content

chore: update Rust to 1.87 #132

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
Jul 10, 2025
Merged

Conversation

uran0sH
Copy link
Contributor

@uran0sH uran0sH commented Jul 9, 2025

Summary of the PR

Update Rust version for using some features available in 1.87, like std::io::pipe

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.

@stefano-garzarella stefano-garzarella enabled auto-merge (rebase) July 9, 2025 16:06
@stefano-garzarella stefano-garzarella enabled auto-merge (rebase) July 10, 2025 07:35
roypat added a commit to roypat/rust-vmm-container that referenced this pull request Jul 10, 2025
Without this, PRs that for example update the rust toolchain (see rust-vmm#132
for an example) will not trigger the workflow, but since the workflow is
required, they will not be able to get merged).

Signed-off-by: Patrick Roy <[email protected]>
roypat added a commit to roypat/rust-vmm-container that referenced this pull request Jul 10, 2025
It's better to build too many docker containers than too few, so let's
go with not triggering the build if we know that only files irrelevant
to the container are modified (instead of trying to explicitly list all
files that are relevant). This way, if the list is stale, we build "too
many" containers, whereas with the current solution, we build "too few"
containers (see for example rust-vmm#132).

Signed-off-by: Patrick Roy <[email protected]>
@stefano-garzarella
Copy link
Member

@uran0sH there is an issue in our CI that we are fixing in #133

When it will be merged, we need to rebase on it to trigger the CI

stefano-garzarella pushed a commit that referenced this pull request Jul 10, 2025
It's better to build too many docker containers than too few, so let's
go with not triggering the build if we know that only files irrelevant
to the container are modified (instead of trying to explicitly list all
files that are relevant). This way, if the list is stale, we build "too
many" containers, whereas with the current solution, we build "too few"
containers (see for example #132).

Signed-off-by: Patrick Roy <[email protected]>
@stefano-garzarella
Copy link
Member

@uran0sH there is an issue in our CI that we are fixing in #133

When it will be merged, we need to rebase on it to trigger the CI

I just rebased, so now everything should go...

@stefano-garzarella stefano-garzarella merged commit d59baa3 into rust-vmm:main Jul 10, 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