Skip to content

Releases: datalad/datalad-dataverse

1.0.3 patch release

29 Oct 14:51
Compare
Choose a tag to compare

1.0.3 (2024-10-29)

Patch release for backwards-compatibility with JülichData (Dataverse 4.20).

Dependencies

  • In conjunction with PR334 a dependency to LooseVersion was introduced.

Bug fixes

  • A version check makes sure that the "format" parameter only gets used with Dataverses of Version 6.0 or higher PR334 by @adswa

1.0.2 (2024-09-19)

19 Sep 12:05
Compare
Choose a tag to compare

Dependencies

  • The dependency on PyDataverse has been set to 0.3.4 or higher: PR330 by @adswa

🐛 Bug fixes

🧪 Tests

  • Appveyor tests are now run weekly in order to find breakage sooner
  • Tests were adjusted to take required metadata specifications directly from the API guide, rather than hard coding: PR299 by @adswa
  • Test helpers accommodate PyDataverse versions 0.3.2+: PR319 by @mih
  • The test suite can now also be run against docker: PR323 by @shoeffner
  • Testremote-calling tests were adjusted to account for an expected failure to replace identical files: PR324 by @adswa

Documentation

  • README badge was updated with a correct link to the docs: PR296 by @behinger)
  • The docs now contain a copy-pastable instruction on DataLad dataset basics: PR301 by @adswa
  • It is now explicit that the next-extension needs to be loaded: PR305 by @bpoldrack
  • The minimum git-annex version for Windows compatibility is now mentioned: PR315 by @mih

1.0.1

20 Apr 09:37
@mih mih
1.0.1
Compare
Choose a tag to compare

1.0.1 (2023-04-20)

🐛 Bug Fixes

  • Wrong argument specification broke the commmand line interface of add-sibling-dataverse. Fixes #289 via #290 (by
    @mih)

🧪 Tests

  • Update tests to use a different metadata format (with fully qualified URLs as keys) that now seems to be required by Dataverse v5.13 (deployed at demo.dataverse.org) #293 (by @mih)

1.0.0 (2022-03-17) -- Dataverse!

17 Mar 20:16
@mih mih
1.0.0
f0bbfd6
Compare
Choose a tag to compare
  • Initial release. See the documentation for a description of the implemented
    functionality.