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.

Sign up for GitHub

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

Jump to bottom

Generate lockfile using the oldest cargo specified #106

Merged
merged 2 commits into from
Dec 6, 2020
Merged

Generate lockfile using the oldest cargo specified #106

merged 2 commits into from
Dec 6, 2020

Conversation

taiki-e
Copy link
Owner

@taiki-e taiki-e commented Dec 6, 2020

Fixes #105

@taiki-e taiki-e force-pushed the generate-lockfile branch 2 times, most recently from c7d422a to c3552eb Compare December 6, 2020 14:40
@taiki-e taiki-e changed the title Generate lock file using the oldest cargo specified Generate lockfile using the oldest cargo specified Dec 6, 2020
@taiki-e
Copy link
Owner Author

taiki-e commented Dec 6, 2020

bors r+

@bors
Copy link
Contributor

bors bot commented Dec 6, 2020

Build succeeded:

@bors bors bot merged commit f5cddf5 into master Dec 6, 2020
@bors bors bot deleted the generate-lockfile branch December 6, 2020 14:51
@taiki-e taiki-e added the A-version Area: --rust-version, --version-range, --version-step label Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
A-version Area: --rust-version, --version-range, --version-step
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Using --version-range in projects that do not contain Cargo.lock is annoying
1 participant
@taiki-e