Dagshub

Latest version: v0.5.9

Safety actively analyzes 723217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 15 of 18

0.2.15

This release has following improvements:
- `dagshub.init()` now respects the passed `host` parameter
- CLI `dagshub upload` now has a `--versioning` parameter that allows you to specified if you want to upload your files with git or dvc. Additionally you can specify this in regular `repo.upload()` calls in python
- Added `tenacity` as a dependency. For now it's only used in streaming filesystem to retry failing downloads when server returns 5xx HTTP codes
- Infrastructure changes - added a `RepoAPI` object that allows you to do a lot of interactions with the repository

0.2.14

Now if you're working in Colab/Jupyter and want to save your progress to a DagsHub repo, you can do it!

python
from dagshub.notebook import save_notebook
save_notebook("user/repository", "my_notebook.ipynb")

0.2.13

- Now any storage you have integrated on your DagsHub repo will show up in a `.dagshub/storage/<schema>/<bucket>` folder and you can access it that way.
- We no longer let you mount multiple DagsHubFilesystem objects in subpaths of each other (e.g. `repo/` and `repo/sub-repo`) to prevent conflicts when trying to download files
- Fixed a bug with listdir caching making it so if you create a new DagsHubFilesystem, you might still be getting `listdir` results from the old one you used previously this session.

0.2.12

Fixed an issue where `dagshub upload --update` didn't work when uploading folders.
We also now handle our backend errors a bit better, in order to provide better feedback to what went wrong

0.2.11

This release includes following improvements:
- Added `rich` for prettier console output. Some functions already utilize it for better UX
- You can now use `dagshub upload` and `repo.upload()` to upload folders
- When asked to perform OAuth authorization, we now open the link in a new browser window

0.2.10

We now no longer print logging informational messages as `log.warning()`, instead using regular `print()`s + `log.info()`
If you want to turn off the print-logging, you can set a `DAGSHUB_QUIET` env var

Also fixed a bug where windows nested paths in DDA uploads were submitting incorrectly

Page 15 of 18

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.