Metaflow

The Metaflow 2.2.5 release is a minor patch release.
- [Features](2.2.5_features)
- Log `metaflow_version:` and `runtime:` tag for all executions

- [Bug Fixes](2.2.5_bugs)
- Handle inconsistently cased file system issue when creating conda environments on macOS for linux-64


<a name="v2.2.5_features"></a> Features
Log `metaflow_version:` and `runtime:` tag for all executions
The tag `metaflow_version:` and `runtime:` is now available for all packaged executions and remote executions as well. This ensures that every run logged by Metaflow will have `metaflow_version` and `runtime` system tags available. PR: 376, 375

<a name="v2.2.4_bugs"></a> Bug Fixes
Handle inconsistently cased file system issue when creating conda environments on macOS for linux-64
Conda fails to correctly set up environments for linux-64 packages on macOS at times due to inconsistently cased filesystems. Environment creation is needed to collect the necessary metadata for correctly setting up the conda environment on AWS Batch. This fix simply ignores the error-checks that conda throws while setting up the environments on macOS when the intended destination is AWS Batch. PR: 377

The Metaflow 2.2.4 release is a minor patch release.
- [Features](2.2.4_features)
- Metaflow is now compliant with AWS GovCloud & AWS CN regions

- [Bug Fixes](2.2.4_bugs)
- Address a bug with overriding the default value for [IncludeFile](https://docs.metaflow.org/metaflow/data#data-in-local-files)
- Port AWS region check for AWS DynamoDb from `curl` to `requests`


<a name="v2.2.4_features"></a> Features
Metaflow is now compliant with AWS GovCloud & AWS CN regions
AWS GovCloud & AWS CN users can now enjoy all the features of Metaflow within their region partition with no change on their end. PR: 364

<a name="v2.2.4_bugs"></a> Bug Fixes
Address a bug with overriding the default value for [IncludeFile](https://docs.metaflow.org/metaflow/data#data-in-local-files)

The Metaflow 2.2.3 release is a minor patch release.
- [Bug Fixes](2.2.3_bugs)
- Fix 305 : Default 'help' for parameters was not handled properly
- Pin the conda library versions for metaflow default dependencies based on the Python version
- Add conda bin path to the PATH environment variable during Metaflow step execution
- Fix a typo in metaflow/debug.py

<a name="v2.2.3_features"></a> Bug Fixes
Fix 305 : Default 'help' for parameters was not handled properly
Fix the issue where default `help` for parameters was not handled properly. 305 Flow fails because `IncludeFile`'s default value for the `help` argument is None. PR: 318

Pin the conda library versions for metaflow default dependencies based on the Python version.
The previously pinned library version does not work with python 3.8. Now we have two sets of different version combinations which should work for python 2.7, 3.5, 3.6, 3.7, and 3.8. PR: 308

Add conda bin path to the PATH environment variable during Metaflow step execution
Previously the executable installed in conda environment was not visible inside metaflow steps. Fixing this issue by appending conda bin path to the PATH environment variable PR: 307

Fix a typo in metaflow/debug.py
A typo fix. PR: 304

The Metaflow 2.2.2 release is a minor patch release.
- [Bug Fixes](2.2.2_bugs)
- Fix a regression introduced in 2.2.1 related to Conda environments
- Clarify Pandas requirements for Tutorial Episode 04
- Fix an issue with the metadata service

<a name="v2.2.2_bugs"></a> Bug Fixes
Fix a regression with Conda
Metaflow 2.2.1 included a commit which was merged too early and broke the use of Conda. This release reverses this patch.

Clarify Pandas version needed for Episode 04
Recent versions of Pandas are not backward compatible with the one used in the tutorial; a small comment was added to warn of this fact.

Fix an issue with the metadata service
In some cases, the metadata service would not properly create runs or tasks.

PRs 296, 297, 298

The Metaflow 2.2.1 release is a minor patch release.
- [Features](2.2.1_features)
- Add `include` parameter to `merge_artifacts`.
- [Bug Fixes](2.2.1_bugs)
- Fix a regression introduced in 2.1 related to S3 datatools
- Fix an issue where Conda execution would fail if the Conda environment was not writeable
- Fix the behavior of uploading artifacts to the S3 datastore in case of retries

<a name="v2.2.1_features"></a>Features
Add `include` parameter for `merge_artifacts`
You can now specify the artifacts to be merged explicitly by the `merge_artifacts` method as opposed to just specifying the ones that should *not* be merged.

<a name="v2.2.1_bugs"></a> Bug Fixes
Fix a regression with datatools
Fixes the regression described in 285.

Fix an issue with Conda in certain environments
In some cases, Conda is installed system wide and the user cannot write to its installation directory. This was causing issues when trying to use the Conda environment. Fixes 179.

Fix an issue with the S3 datastore in case of retries
Retries were not properly handled when uploading artifacts to the S3 datastore. This fix addresses this issue.


PRs 282, 286, 287, 288, 289, 290, 291

The Metaflow 2.2.0 release is a minor release and introduces [Metaflow's support for R lang](https://docs.metaflow.org/v/r/).
- [Features](2.2.0_features)
- Support for R lang.

<a name="v2.2.0_features"></a> Features
Support for R lang.
This release provides an [idiomatic API to access Metaflow in R lang](https://docs.metaflow.org/v/r/). It piggybacks on the Pythonic implementation as the backend providing most of the functionality previously accessible to the Python community. With this release, R users can structure their code as a metaflow flow. Metaflow will [snapshot the code, data, and dependencies](https://docs.metaflow.org/v/r/metaflow/basics#the-structure-of-metaflow-code) automatically in a content-addressed datastore allowing for [resuming of workflows](https://docs.metaflow.org/v/r/metaflow/debugging#how-to-debug-failed-flows), [reproducing past results, and inspecting anything about the workflow](https://docs.metaflow.org/v/r/metaflow/client) e.g. in a notebook or RStudio IDE. Additionally, without any changes to their workflows, users can now [execute code on AWS Batch and interact with Amazon S3 seamlessly](https://docs.metaflow.org/v/r/metaflow/scaling).

PR 263 and PR 214 .