Skip to content

Releases: estuary/flow

v0.6.5

25 Mar 16:03

Choose a tag to compare

This release includes support for the upcoming materialization triggers feature, in addition to several other bugfixes and improvements.

What's Changed

v0.6.4

02 Mar 19:34

Choose a tag to compare

This release includes some bug fixes to some validation behavior in cases where a key field has a default annotation

v0.6.3

18 Feb 16:56

Choose a tag to compare

This release includes bug fixes for flowctl discover, and adds several new flowctl alert-subscriptions subcommands for managing alert subscriptions via the CLI.

v0.6.2

20 Jan 18:33

Choose a tag to compare

This release includes internal updates to flowctl for continued compatibility with directly reading collection data.

v0.6.1

08 Jan 18:13

Choose a tag to compare

v0.6.1 Pre-release
Pre-release

Just updating dependencies and our build process

dev-next

26 Nov 22:09

Choose a tag to compare

dev-next Pre-release
Pre-release

This is the latest development build, which gets updated on every successful build of the master branch.

v0.6.0

31 Oct 11:42

Choose a tag to compare

This flowctl release includes some exciting new features, and also a few breaking changes to command line options.

The biggest news is that flowctl now supports Python derivations in flowctl preview! We'll be rolling out support for Python derivations on private data planes shortly. Python derivations are not currently supported on our public data planes.

Additionally, the catalog list and catalog history commands now have a --models argument, which can be used in conjunction with --output json|yaml to include the models in the output. This can't be used with the default table output.

This update introduces some breaking changes to flowctl options as we migrate functionality to our GraphQL API. This will help us scale and streamline our workflows for the future.

We tried to limit breaking changes to options that aren't widely used. However, if you use flowctl in automated contexts, it would be wise to check your scripts for usage of any of the following before updating to the latest version of flowctl.

flowctl catalog list:

  • --captures, --collections, --materializations, and --tests are now standalone flags rather than accepting boolean arguments. For example, instead of --captures=true, use --captures.
  • Each flowctl catalog list command may only include one of the --captures, --collections, --materializations, or --tests options. Run flowctl catalog list multiple times if you need to list multiple types of resources.
  • The --data-plane-name argument can only be provided at most once, where previously you could provide multiple values. Run flowctl catalog list multiple times if you need to list specs for multiple specific data planes.
  • For those cosmopolitan users who have access to more than 5 different catalog namespaces, you'll now be required to pass an explicit --prefix argument.

flowctl catalog status:

  • The format of --output json|yaml has changed, with renamed and moved fields. However, the table output should remain the same.

v0.5.24

08 Oct 14:30

Choose a tag to compare

Minor updates to support new reduce annotations when running locally.

v0.5.22

18 Sep 19:49

Choose a tag to compare

What's Changed

This release introduces support for the new redact annotation, which enables blocking or hashing portions of documents very early in capture process.

It also adds a new flowctl discover subcommand, which enables CLI-driven capture creation workflows.

New Contributors

Full Changelog: v0.5.21...v0.5.22

v0.5.21

28 Aug 16:58
312dbba

Choose a tag to compare

Includes some minor updates related to flowctl catalog status