Add a Cargo.lock to the registry crate #190
Merged
Conversation
This file contains 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
|
We want s3 by default! |
mara-schulke
approved these changes
Dec 7, 2023
qsantos
force-pushed
the
registry-cargo-lock
branch
from
4db799a to
6258af9
Compare
qsantos
force-pushed
the
registry-cargo-lock
branch
from
6258af9 to
dfbc1da
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR:
registry/Cargo.lock, which was ignored, to the repositorysqlx, which will need to be re-added when it is actually used); this will make compilation faster until these dependencies are actually neededmake the S3 storage feature non-default; this should make compilation faster assuming we generally just want a filesystem storageproto/vendor/directory which is generated bybuild.rsIf you think any of these should not be done, I'll just remove the corresponding commit.