chore: commit Cargo.lock file to make builds more predictable
#1190
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andygrove
approved these changes
Feb 27, 2025
Contributor
Author
|
it looks like intermittent failure on docker container creation, I can't really re run it |
milenkovicm
force-pushed
the
chore_fix_crono
branch
from
66a3329 to
2a3482e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
as discussed in
Cargo.lockdatafusion#14483committing
Cargo.lockto gitWhat changes are included in this PR?
Cargo.lockfrom.gitignorechronodependency to0.4.39(current arrow version (53) is not covered by the emergency release (54.2.1), so this is only option to get it building)Are there any user-facing changes?