This repository has been archived by the owner on Sep 13, 2023. It is now read-only.
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 contains the following updates:
~=2.0
->~=3.1
Release Notes
iterative/dvc
v3.1.0
Compare Source
What's Changed
🚀 New Features and Enhancements
🐛 Bug Fixes
Other Changes
Full Changelog: iterative/dvc@3.0.0...3.1.0
v3.0.0
Compare Source
What's Changed
🛠 Breaking Changes
DVC used to identify a file by removing CRLF line endings (although it stored the original file contents in the cache).
However, in DVC 3.x, this behaviour has been dropped.
Now, DVC hashes the file contents directly without removing CRLF line endings.
All pre-existing DVC-tracked data from DVC 2.x can still be accessed and used in DVC 3.x. However, any new operations that result in a DVC committed change will generate a 3.x DVC output, which will be stored in a different location than 2.x DVC outputs.
The files will be stored in cache at
.dvc/cache/files/md5
and in the remote at<remote_dir>/files/md5
.You can read more about it in #4658 and #9538.
While strictly not required,
dvc cache migrate
command is introduced to migrate 2.x format of cache to 3.x format to make migrations easier (#9591).Support for tracking (cached) external outputs has been removed (#9570).
checkpoints
has been removed (#9271).dvc run
command has been removed, usestage add --run
instead (#9508).exp init
,exp gc
commands have been removed (#9269, #9273).--show-json
/--show-md
/--show-csv
flags are removed (#9475). Use--json
/--md
/--csv
instead.--recursive
option fromdvc add
is removed (#9513). Usedvc add dir
to recursively add files in a directory.--file
option fromdvc add
,dvc import
anddvc import-url
is now removed (#9547, #9562, #9548).--meta
,--desc
,--label
, and--type
option fromdvc add
,dvc import
anddvc import-url
is now removed (#9481).--jobs
option that is used in combination withdvc add --to-remote
is now renamed to--remote-jobs
to avoid confusion withcore.checksum_jobs
(#9522, #9550).--metrics
option is removed from bothexp run
andrepro
commands (#9458).--pcp
option fromexp show
has been removed (#9270).Read-only support for dvc 1.0 lockfile format has been removed (#9476).
Support for defining multiple plots as a dictionary has been removed (#9486). Use a list instead.
dvc.yaml: stage-level
vars
is removed (#9556).use of
.dvc
file as a pipeline stage has been removed, which has been deprecated in 1.0. This means that now it is forbidden to useparams
/cmd
/metrics
/plots
in.dvc
files (#9546, #9551, #9552, #9554). Also, if you have used dvc before1.0
,Dvcfile
is no longer supported or recognized.pkg
info has moved fromdvc.utils.pkg
todvc._build
. You can now import it usingfrom dvc import PKG
(#9559).🐛 Bug Fixes
Full Changelog: iterative/dvc@2.58.2...3.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.