Skip to content

Remove lockfiles from being tracked #498

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
Aug 6, 2025
Merged

Conversation

mxgrey
Copy link
Collaborator

@mxgrey mxgrey commented Jul 18, 2025

As discussed in the working group meeting, once the lockfiles were committed, we wound up having a lot more unnecessary churn in the git history, and more crucially we started seeing breakages in the "Rust Minimal" CI due to new lockfiles being generated that are incompatible with Rust compiler version 1.75.

This PR reverts our practices by removing the lockfiles and putting Cargo.lock back into the .gitignore list.

@jhdcs
Copy link
Collaborator

jhdcs commented Jul 18, 2025

The CI still seems to be failing even with the lockfile removed. Is this expected behavior?

@mxgrey
Copy link
Collaborator Author

mxgrey commented Jul 18, 2025

The CI for Rust Minimal and Rust Windows will continue to fail for all PRs until ros2-rust/rosidl_runtime_rs#13 is merged upstream.

Copy link
Collaborator

@luca-della-vedova luca-della-vedova left a comment

Choose a reason for hiding this comment

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

I'm seeing CI failures on #492 precisely due to this lockfile issue, CI seems to be good here

@jhdcs
Copy link
Collaborator

jhdcs commented Aug 6, 2025

Sorry for the delay. This looks good to me as well.

Merging now.

@jhdcs jhdcs merged commit cc49a39 into ros2-rust:main Aug 6, 2025
9 of 14 checks passed
@mxgrey mxgrey deleted the remove_lockfiles branch August 11, 2025 13:04
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