v0.9.0

AiiDA version: To be released

Update repository with export archive for export version 0.9.
The file follows the naming of previous export version files having the suffix _manual, since it was not produced properly, i.e., through a new workflow run in AiiDA.
Instead, the export file export_v0.8_manual.aiida has been the unpacked, updated manually, and repacked.
This means the latest "proper" export file is export_v0.4.aiida.

Changes are expected to be released with AiiDA version 1.2.0.

New file: export_v0.9_manual.aiida

v0.8.0

AiiDA version: 1.0.0

Update repository with export archive for export version 0.8.
The file follows the naming of previous export version files having the suffix _manual, since it was not produced properly, i.e., through a new workflow run in AiiDA.
Instead, the export file export_v0.7_manual.aiida has been the unpacked, updated manually, and repacked.
This means the latest "proper" export file is export_v0.4.aiida.

Changes are expected to be released with AiiDA version 1.0.1.

New file: export_v0.8_manual.aiida

v0.7.0

AiiDA version: 1.0.0b4

Update repository with export archive for export versions 0.6 and 0.7.
These files are named differently, having the suffix _manual, since they were not produced properly, through a new workflow run in AiiDA.
Instead, the export file export_v0.4.aiida has been the unpacked, updated manually, and repacked.

The file export_v0.5.aiida has also been made this way, and will therefore have its name changed accordingly.

New files:

• export_v0.5_manual.aiida (only the filename has been altered)
• export_v0.6_manual.aiida
• export_v0.7_manual.aiida

v0.5.2

AiiDA version: 1.0.0b3

Remove test files according to issue #6.
The files have been moved to aiida-core under aiida.backends.tests.tools.importexport.migration..
As explained in the issue, the problem of having tests that concern files in aiida-core, is that they cannot be skipped with a helpful message using unittest.skip(<message>).

This repository has now become the keeper of the export archives and the workflows that created them.
Hence, it should only ever be touched, when a new export version is introduced in AiiDA, and a new archive must be added.

v0.5.1

AiiDA version: 1.0.0b3

Update imports from aiida-core in accordance with the restructuring of the import/export-module.
For a reference, this was done in aiida-core PR #3052.

v0.5.0

AiiDA version: 1.0.0b3

Update version number of this repository to reflect the current EXPORT_VERSION in aiida_core.
The version number is now as follows: <EXPORT_VERSION>.<patch>

Implement initial change related to the update of EXPORT_VERSION from 0.4 to 0.5:

• Migration 0034: Remove fields/columns "nodeversion" and "public" from the DbNode model.
• Migration 0036: Remove field/column "transport_params" from the DbComputer model.

Note: The newly created export_v0.5.aiida under /aiida-export-migration-tests/archives is not actually created from an AiiDA workflow, but instead a migration of export_v0.4.aiida.
This is because the changes between the versions are insignificant for the outcome of the workflow, and that only very minor changes have occurred.

v0.1.1

Patch to v0.1.0.

AiiDA version: 1.0.0

Minor fixes due to changes in aiida-core.

Folder fixtures changes name to archives to match the same change happening for aiida-core.
The simple AiiDA export archives in aiida-core representing the different export versions have changed names:

• export_v0.1_no_UPF.aiida -> export_v0.1_simple.aiida
• export_v0.2_no_UPF.aiida -> export_v0.2_simple.aiida
• export_v0.3_no_UPF.aiida -> export_v0.3_simple.aiida
• export_v0.4_no_UPF.aiida -> export_v0.4_simple.aiida

A change in the conversion message included in metadata.json files, when a migration has been successfully performed, introduces the version of AiiDA into the message. In order to have the tests be version-agnostic, the conversion_info key has to be handled specially in the relevant tests.
When migrating an archive, it is asserted that the correct conversion message appears in the migrated archive, and the conversion_info item is then popped from both the migrated archive and the archive imported for comparison.

v0.1.0

First release, v0.1.0.

This version is meant to be installed by AiiDA v1.0.0 and was made when AiiDA v1.0.0b2 was the newest version.