[dagster-cloud-action] automatically bump version action tag

[cmpadden]

Closes ADOPT-1920

After chatting with @gibsondan a bit more, we think it would be better to keep the v0.1 and then dynamically update it to the latest version on the release branch creation following the same pattern as the Docker image tag.

You can find an example of the updated Docker tag for a release here:

• https://github.com/dagster-io/dagster-cloud-action/blob/release-1.11.13/gitlab/hybrid-ci.yml#L32

▸ uv run scripts/release.py update-action-version-references 1.11.12
Updating action version references to v1.11.12
github/serverless/branch_deployments.yml
github/serverless/deploy.yml
github/serverless/dbt/branch_deployments.yml
github/serverless/dbt/deploy.yml

▸ git diff .
diff --git a/github/serverless/branch_deployments.yml b/github/serverless/branch_deployments.yml
index 30d2c9a..ac3e565 100644
--- a/github/serverless/branch_deployments.yml
+++ b/github/serverless/branch_deployments.yml
@@ -24,12 +24,12 @@ jobs:
     steps:
       - name: Prerun Checks
         id: prerun
-        uses: dagster-io/dagster-cloud-action/actions/utils/prerun@v0.1
+        uses: dagster-io/dagster-cloud-action/actions/utils/prerun@v1.11.12

       - name: Launch Docker Deploy
         if: steps.prerun.outputs.result == 'docker-deploy'
         id: parse-workspace
-        uses: dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v0.1
+        uses: dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v1.11.12
         with:
           dagster_cloud_file: $DAGSTER_CLOUD_FILE

@@ -42,7 +42,7 @@ jobs:

       - name: Python Executable Deploy
         if: steps.prerun.outputs.result == 'pex-deploy'
-        uses: dagster-io/dagster-cloud-action/actions/build_deploy_python_executable@v0.1
+        uses: dagster-io/dagster-cloud-action/actions/build_deploy_python_executable@v1.11.12
         with:
           dagster_cloud_file: "$GITHUB_WORKSPACE/project-repo/$DAGSTER_CLOUD_FILE"
           build_output_dir: "$GITHUB_WORKSPACE/build"
@@ -65,7 +65,7 @@ jobs:
         with:
           ref: ${{ github.head_ref }}
       - name: Build and deploy to Dagster Cloud serverless
-        uses: dagster-io/dagster-cloud-action/actions/serverless_branch_deploy@v0.1
+        uses: dagster-io/dagster-cloud-action/actions/serverless_branch_deploy@v1.11.12
         with:
           dagster_cloud_api_token: ${{ secrets.DAGSTER_CLOUD_API_TOKEN }}
           location: ${{ toJson(matrix.location) }}
diff --git a/github/serverless/dbt/branch_deployments.yml b/github/serverless/dbt/branch_deployments.yml
index 277bcbb..038cf06 100644
--- a/github/serverless/dbt/branch_deployments.yml
+++ b/github/serverless/dbt/branch_deployments.yml
@@ -26,12 +26,12 @@ jobs:
     steps:
       - name: Prerun Checks
         id: prerun
-        uses: dagster-io/dagster-cloud-action/actions/utils/prerun@v0.1
+        uses: dagster-io/dagster-cloud-action/actions/utils/prerun@v1.11.12

       - name: Launch Docker Deploy
         if: steps.prerun.outputs.result == 'docker-deploy'
         id: parse-workspace
-        uses: dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v0.1
+        uses: dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v1.11.12
         with:
           dagster_cloud_file: $DAGSTER_CLOUD_FILE

[github-actions]

Your pull request is automatically being deployed to Dagster Cloud.

Location	Status	Link	Updated
from_gh_action		View in Cloud	Oct 03, 2025 at 04:16 PM (UTC)

[gibsondan]

thx! lets keep an eye after the next OSS release and verify this worked the way we expect it to

The specific tag to clone from is still hardcoded in the dagit server for now right?

[cmpadden]

thx! lets keep an eye after the next OSS release and verify this worked the way we expect it to

The specific tag to clone from is still hardcoded in the dagit server for now right?

Confirmed that the tag was updated in the latest deployment.

https://github.com/dagster-io/dagster-cloud-action/blob/v1.11.14/github/serverless/deploy.yml