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

Update cargo lock format #43

Merged
merged 2 commits into from
May 6, 2020
Merged

Update cargo lock format #43

merged 2 commits into from
May 6, 2020

Conversation

anupdhml
Copy link
Contributor

@anupdhml anupdhml commented May 6, 2020

Update to cargo's new lock file format.

Done via:

cargo install cargo-lock 
cargo lock translate > Cargo.lock

Also ran cargo update at the end. This will help us resolving merge conflicts in #33 easily (when merging master there).

@codecov
Copy link

codecov bot commented May 6, 2020

Codecov Report

Merging #43 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master     #43   +/-   ##
======================================
  Coverage    0.00%   0.00%           
======================================
  Files           7       7           
  Lines         274     274           
======================================
  Misses        274     274           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c45b23c...ba0a8fd. Read the comment docs.

Copy link
Member

@darach darach left a comment

Choose a reason for hiding this comment

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

LGTM

@darach darach merged commit dbc7f51 into master May 6, 2020
@darach darach deleted the update_lock_format branch May 6, 2020 19:33
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