v2.1.0

What's Changed

• Modify metagenome_annotation_id to was_generated_by by @kheal in #25

New Contributors

• @kheal made their first contribution in #25

Full Changelog: v0.10.2...v2.1.0

v2.0.0

What's Changed

• Automatically synchronize VERSION file with Release tag name by @eecavanna in #21
• berkeley metaproteomics aggregation updates PR by @aclum in #18

New Contributors

• @aclum made their first contribution in #18

Full Changelog: v0.10.1...v2.0.0

v0.10.2: Testing Berkeley-specific changes

⚠️ @eecavanna accidentally merged the Berkeley-specific changes into main.

What's Changed

• Automatically synchronize VERSION file with Release tag name by @eecavanna in #21
• DO NOT MERGE berkeley metaproteomics aggregation updates PR by @aclum in #18

New Contributors

• @aclum made their first contribution in #18

Full Changelog: v0.10.1...v0.10.2

v0.10.1: Testing branch `10-berkeley-update-generate_metap_aggpy`

This is a non-production Release related to the Berkeley schema.

What's Changed

• generate aggregation results for COG and Pfam. Add tests by @chienchi in #14
• Document process of setting up local development environment by @eecavanna in #16
• 8 update generate functional aggpy to also include metatranscriptome annotation set by @chienchi in #17
• Update functional_agg to use workflow_execution_set by @mbthornton-lbl in #19

New Contributors

• @chienchi made their first contribution in #14
• @mbthornton-lbl made their first contribution in #19

Full Changelog: v0.0.010...v0.10.1

v1.0.8

What's Changed

• Document process of setting up local development environment by @eecavanna in #16
• 8 update generate functional aggpy to also include metatranscriptome annotation set by @chienchi in #17

Full Changelog: v1.0.7...v1.0.8

v1.0.7

What's Changed

• Generate aggregation results for COG and Pfam, and add tests by @chienchi in #14

New Contributors

• @chienchi made their first contribution in #14

Full Changelog: v0.0.1...v1.0.7

v0.10.0: Testing branch `10-berkeley-update-generate_metap_aggpy`

This "pre-release" was created so we could take advantage of the existing "plumbing" that builds container images and publishes them to GHCR when a Release gets created. The version number was chosen to stand out from "real" versions. Here's the naming convention I established—then followed—with this release:

v0.{issue_number}.{build_number}:

• issue_number is the issue number that the Release (i.e. the Release's tag) is associated with
• build_number is an arbitrary number you assign to this build

Full Changelog: v0.0.1...v0.10.0

v1.0.6

What's Changed

• Disable debug logs by @eecavanna in #7

Full Changelog: v1.0.5...v1.0.6

v1.0.5

What's Changed

• Unwrap rows from kegg_term_counts dictionary by @eecavanna in #6

Full Changelog: v1.0.4...v1.0.5

v1.0.4

What's Changed

• Print the rows value to help with debugging by @eecavanna in #5

Full Changelog: v1.0.3...v1.0.4