Releases: microbiomedata/nmdc-aggregator
Releases · microbiomedata/nmdc-aggregator
v2.2.2
v2.2.1
Updates to environmental variable names.
Full Changelog: v2.2.0...v2.2.1
v2.2
What's Changed
- Refactor metaproteomics aggregation script by @kheal in #27
This includes updates metaproteomics records to populate functional_annotation_agg which is already defined in the schema and now uses nmdc runtime to add new documents instead of pymongo.
Full Changelog: v2.1.0...v2.2.0
v2.1.0
v2.0.0
v0.10.2: Testing Berkeley-specific changes
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
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
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 withbuild_number
is an arbitrary number you assign to this build
Full Changelog: v0.0.1...v0.10.0