diff --git a/.github/workflows/CD_dagster_branch.yml b/.github/workflows/CD_dagster_branch.yml index 040f4737..8923287a 100644 --- a/.github/workflows/CD_dagster_branch.yml +++ b/.github/workflows/CD_dagster_branch.yml @@ -92,7 +92,7 @@ jobs: # working tree either path sets up below. - name: Prerun checks id: prerun - uses: dagster-io/dagster-cloud-action/actions/utils/prerun@v1.13.19 + uses: dagster-io/dagster-cloud-action/actions/utils/prerun@v1.13.20 # parse_workspace performs its own `actions/checkout`, which cleans the # working tree -- fine here because the Docker path runs in a separate job @@ -100,7 +100,7 @@ jobs: - name: Parse dagster_cloud.yaml if: steps.prerun.outputs.result == 'docker-deploy' id: parse - uses: dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v1.13.19 + uses: dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v1.13.20 with: dagster_cloud_file: ${{ env.DAGSTER_CLOUD_FILE }} @@ -154,7 +154,7 @@ jobs: # dependency hash changes. - name: Deploy to Dagster+ branch deployment if: steps.prerun.outputs.result == 'pex-deploy' - uses: dagster-io/dagster-cloud-action/actions/build_deploy_python_executable@v1.13.19 + uses: dagster-io/dagster-cloud-action/actions/build_deploy_python_executable@v1.13.20 with: dagster_cloud_file: "$GITHUB_WORKSPACE/project-repo/${{ env.DAGSTER_CLOUD_FILE }}" build_output_dir: "$GITHUB_WORKSPACE/build" @@ -257,7 +257,7 @@ jobs: # checkout_repo is false because requirements.txt is generated above and # a second checkout would discard it. - name: Deploy to Dagster+ branch deployment - uses: dagster-io/dagster-cloud-action/actions/serverless_branch_deploy@v1.13.19 + uses: dagster-io/dagster-cloud-action/actions/serverless_branch_deploy@v1.13.20 with: organization_id: ${{ vars.DAGSTER_CLOUD_ORGANIZATION_ID }} dagster_cloud_api_token: ${{ secrets.DAGSTER_CLOUD_API_TOKEN }} diff --git a/.github/workflows/CD_dagster_prod.yml b/.github/workflows/CD_dagster_prod.yml index 83333248..69be96d6 100644 --- a/.github/workflows/CD_dagster_prod.yml +++ b/.github/workflows/CD_dagster_prod.yml @@ -94,7 +94,7 @@ jobs: # working tree either path sets up below. - name: Prerun checks id: prerun - uses: dagster-io/dagster-cloud-action/actions/utils/prerun@v1.13.19 + uses: dagster-io/dagster-cloud-action/actions/utils/prerun@v1.13.20 # parse_workspace performs its own `actions/checkout`, which cleans the # working tree -- fine here because the Docker path runs in a separate job @@ -102,7 +102,7 @@ jobs: - name: Parse dagster_cloud.yaml if: steps.prerun.outputs.result == 'docker-deploy' id: parse - uses: dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v1.13.19 + uses: dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v1.13.20 with: dagster_cloud_file: ${{ env.DAGSTER_CLOUD_FILE }} @@ -155,7 +155,7 @@ jobs: # spins up when the dependency hash changes. - name: Deploy to Dagster+ prod if: steps.prerun.outputs.result == 'pex-deploy' - uses: dagster-io/dagster-cloud-action/actions/build_deploy_python_executable@v1.13.19 + uses: dagster-io/dagster-cloud-action/actions/build_deploy_python_executable@v1.13.20 with: dagster_cloud_file: "$GITHUB_WORKSPACE/project-repo/${{ env.DAGSTER_CLOUD_FILE }}" build_output_dir: "$GITHUB_WORKSPACE/build" @@ -203,7 +203,7 @@ jobs: # checkout_repo is false because requirements.txt is generated above and # a second checkout would discard it. - name: Deploy to Dagster+ prod - uses: dagster-io/dagster-cloud-action/actions/serverless_prod_deploy@v1.13.19 + uses: dagster-io/dagster-cloud-action/actions/serverless_prod_deploy@v1.13.20 with: organization_id: ${{ vars.DAGSTER_CLOUD_ORGANIZATION_ID }} dagster_cloud_api_token: ${{ secrets.DAGSTER_CLOUD_API_TOKEN }}