v0.2.6

Fixed a bug where the custom Dockerfile argument introduced in v0.2.5 would conditionally not work.

v0.2.5: Merge pull request #19 from dagster-io/benpankow/add-dockerfile-name-arg

Added the ability to specify a non-standard Dockerfile using the dockerfile property in your locations.yaml file.

v0.2.4

Added a container_context field that can be used to customize a code location for a specific execution environment (like Kubernetes, Docker, or ECS). See https://docs.dagster.cloud/guides/adding-code#environment-specific-config for more information.

v0.2.3

The code previews action now correctly uses the pull request HEAD commit to tag its generated images. Previously, it was using the merge commit.

v0.2.2

Added a publish-only action which can be used with a custom build and push process to notify Cloud of updated code locations. See the examples folder for more details.

v0.2.1

Automatically include git metadata in deployed code locations.

v0.2.0

• Add support for creating Dagster code previews.
• Github actions in this repository are now differentiated by paths.

Name	Before v0.2.0	v0.2.0
Update Code Locations	dagster-io/[email protected]	dagster-io/dagster-cloud-cicd-action/[email protected]
Code Previews	N/A	dagster-io/dagster-cloud-cicd-action/[email protected]

v0.1.2

Add support for the module_name, working_directory, executable_path, and attribute properties in a locations.yaml file.

v0.1.1

Add support for specifying a Docker target stage for multistage Dockerfiles in locations.yaml file

v0.1.0

Initial release, supporting build via Dockerfile or requirements.txt