v2.1.39

Support creation of dataset revision with multiple previous revisions via the existing previous_revision_uuid field (for backward compatibility)

v2.1.38

• Add new endpoint GET /datasets/<id>/multi-revisions

v2.1.37

• Change dataset_is_primary to use creation_action to determine whether a dataset is primary rather than inspecting its distance from the nearest sample ancestor

v2.1.36

• Add creation_action to Dataset/Publication to handle multi-assay creation
• Update commons to 2.1.12 and used pinned Werkzeug 2.3.7
• Reindex collection at creation and update
• Remove deprecated GET /collections and GET /collections/<id> calls
• Fix to api yaml to make it valid yaml
• Forward docker logs to AWS CloudWatch

Full Changelog: v2.1.35...v2.1.36

v2.1.35

Status history tracking for Dataset/Publication/Upload with new field status_history

v2.1.34

• Remove trigger method and neo4j method for updating ancestors data_access_level
• Add new endpoint and neo4j queries to handle GET /siblings/<id>

v2.1.33

• Add logic for processing the dataset_uuids field of a PUT request via trigger logic, fixing defect noted in which Collection Dataset members cannot be updated.
• Remove support for /collections/<collection_uuid>/add-datasets route.
• Remove app.py add_datasets_to_collection().
• Remove app_neo4j_queries.py add_datasets_to_collection().
• 32x8 -> 16x16 for EC2 PROD VM downgrade to accommodate c5.18xlarge -> c5.4xlarge

v2.1.32

Support Publication type in access visibility check

v2.1.31

• Remove cache from normalized response to ensure data integrity
• Only return metadata of neo4j nodes for read trigger to limit the nested fields and avoid performance overhead

v2.1.30

• Fix caching issue when skipped properties is used
• Update to use commons 2.1.8