0.4.0

• Unsupported input types will now transparently re-use values taken from executions (on relaunch) or default values specified by the selected launch plan. This makes it possible to launch/re-launch workflows which use unsupported input types if the user does not want to edit the value.
• Searchable selector in launch form will now highlight value on focus, instead of clearing it.
• Fixed bugs with default/copied values for inputs in the launch form.
• Added Pull Request template.

v0.3.2

Fixes some reference errors due to dependency updates.

flyteorg/flyte#179
flyteorg/flyte#182

v0.3.1

• Fixed a bug with searching for workflow versions in the context of relaunching an execution
• Updated Webpack config to fix issues trying to build the Docker image

v0.3.0

• Admin requests no longer use the local CORS proxy
• Added Authentication support
• Dependency updates
• Added support for Collection input types in the Launch form
• Added validation for inputs in the Launch form
• Various bug fixes related to the Launch form
• Relaunching an Execution will now populate a Launch from with the values used in that execution, allowing the user to modify the Workflow version, LaunchPlan, or input values before launching again
• Input values in the Launch form are maintained (if possible) between changes to the Workflow version or LaunchPlan

0.2.1

Bug Fixes

• (flyteorg/flyte#98) Ensure that inputs/outputs are sorted by key to provide a consistent display experience
• Make sure .snyk file exists at the proper time during Docker builds

0.2.0

• Minor fixes to Launch form
• Updated execution input display to support remote storage
• Styling update to projects list page
• Added support for rendering project descriptions
• Fixed sort order on project list page
• Added support for descriptions on workflows
• Added Tasks list view
• Security/dependency updates
• Updated logo/favicon

Initial FlyteConsole Release

Merge pull request #5 from lyft/launch

Adds support for launching workflows