Skip to content

Releases: Netflix/metaflow

2.15.4

05 Mar 11:17
f66ad38
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.15.3...2.15.4

2.15.3

03 Mar 17:13
99fdad2
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.15.2...2.15.3

2.15.2

01 Mar 02:45
71a5e8c
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.15.1...2.15.2

2.15.1

28 Feb 22:01
a5da3dc
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.15.0...2.15.1

2.15.0

25 Feb 20:30
b987b91
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.14.3...2.15.0

2.14.3

22 Feb 03:42
c1def39
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.14.2...2.14.3

2.14.2

21 Feb 19:11
d83577f
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.14.1...2.14.2

2.14.1

20 Feb 23:54
e8efc78
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.14.0...2.14.1

2.14.0

11 Feb 18:41
8d91c06
Compare
Choose a tag to compare

Improvements

Fix regression with Metaflow Deployer

This release reverts a change that caused the Metaflow deployer for Argo Workflows and AWS Step Functions not to work.

Minor version bump

The minor version is being bumped due to last releases #2243 changing defaults for artifact serialization, even though these should not have any functional effect with Python versions >=3.4

Connection pooling for metadata service

Improves the time it takes to launch the first task by using a connection pool for the metadata service traffic

What's Changed

Full Changelog: 2.13.10...2.14.0

2.13.10

11 Feb 13:47
fa456c2
Compare
Choose a tag to compare

Features

Argo Workflows for Incident.io alerts

This release introduces support for Incident.io alerts with Argo Workflows. In order to enable these, some additional configuration is required compared to other notification implementations.

as an example

python alerting_flow.py argo-workflows create \
--notify-on-error \
--notify-on-success \
--notify-incident-io-api-key API-KEY \
--incident-io-error-severity-id ERROR-ID \
--incident-io-success-severity-id SUCCESS-ID

The API key used should have permissions to create incidents.

The severity ID's are a requirement from incident.io as this is how alerts are categorized. All severity ID's are account based and users can create new ones as they please, which is why we must set ones as part the flow deployment.

Improvements

Default to Pickle protocol 4 for artifacts

This release changes the default artifact serialization to use protocol 4 for pickling. The change should lead to storage savings in small (<2 GB) artifacts along with faster serializations due to skipping trying protocol 2 first.

What's Changed

New Contributors

Full Changelog: 2.13.9...2.13.10