Remove step from dagster-cloud-action release where you merge the release tag change back into master (#224)

Summary:
We haven't actually merged the release branch back into master in a while, and I can't think of a good reason to do so. This brings our release process in line with the OSS release process for other repos where there's a dev tag in master and we push from release branches.

Test Plan:
Run release script, verify resulting code changes

Author: gibsondan

CONTRIBUTING.md

@@ -12,7 +12,7 @@ If you have a PAT handy you can just do:
 % echo $YOUR_GITHUB_PAT | docker login ghcr.io -u $YOUR_GITHUB_USERNAME --password-stdin
 ```
 
-## Step 2. Determine the new point version and create a release branch,
+## Step 2. Determine the new point version and create a release branch.
 
 ```
 % git checkout main
@@ -22,24 +22,11 @@ pex-v0.1
 pex-v0.1.14
 prha
 v0.1
-v0.1.10
-v0.1.11
-v0.1.12
-v0.1.13
-v0.1.14
-v0.1.15
-v0.1.16
-v0.1.17
-v0.1.18
-v0.1.19
-v0.1.20
-v0.1.21
+v1.10.12
 ```
 
-The point version is the next unused `v0.1.*` version, eg `v0.1.22` above. Create a release branch
-
 ```
-% git checkout -b release-0.1.22
+% git checkout -b release-1.10.13
 ```
 
 ## Step 3. Build and deploy a new docker-cloud-action image, a new dagster.cloud.pex and update code references to docker
@@ -48,8 +35,7 @@ A script does this work. **Note**: a virtual environment using Python3.11 is req
 
 ```bash
 # Note no 'v' prefix
-# This accepts `NEW_VERSION OLD_VERSION` so it can update code references from the old to the new version.
-python scripts/release.py create-rc 0.1.22 0.1.21
+python scripts/release.py create-rc 1.10.13
 ```
 
 This leaves uncommitted changes in the working directory.
@@ -64,17 +50,17 @@ git diff
 git add . && git commit -m "Rebuild"
 
 # Tag: using '-a' lets us add an annotation message, typically we use the version "v0.1.22"
-git tag -a v0.1.22
+git tag -a v1.10.13
 ```
 
 # Step 5. Push and Test
 
 ```bash
 # push the release branch
-git push --set-upstream origin release-0.1.22
+git push --set-upstream origin release-1.10.13
 # push the tag
-git push origin v0.1.22
-# to test, change the reference in a github workflow yaml file `@v0.1 -> @v0.1.22` and `@pex-v0.1 -> @v0.1.22`
+git push origin v1.10.13
+# to test, change the reference in a github workflow yaml file `@v0.1 -> @v0.1.22` and `@pex-v0.1 -> @v1.10.13`
 # see also dagster-cloud-action-test
 ```
 
@@ -92,53 +78,17 @@ Hybrid:
 If you make any changes and rebuild the rc, you need to retag and push the release tag:
 
 ```bash
-python scripts/release.py create-rc 0.1.22 0.1.21
+python scripts/release.py create-rc 1.10.13
 
 # the only autogenerated change should be to the pex file because changes to the yamls have already committed
 
 # -f to force since the tag exists
-git tag -f -a v0.1.22
-git push -f origin v0.1.22
+git tag -f -a v1.10.13
+git push -f origin v1.10.13
 
 # test again, fix and repeat
 ```
 
-# Step 6. Promote
-Most users point at a dot version tag for the GitHub Action, e.g. `@v0.1` and `@pex-v0.1`.
-If you are releasing a fix or non-breaking feature, you want to move this tag so existing users get access to your changes.
-
-> Due an unfortunate bug, the ci-summary step in many user's workflow is pinned to v0.1.27, so we need v0.1.27 to follow v0.1 as well.
-> See https://github.com/dagster-io/dagster-cloud-hybrid-quickstart/commit/2149359dd1076f3bcd6f652dc00cb74ac9c81636
-
-```bash
-# use '-f' to force move the tag, since these tags already exist
-git tag -f v0.1 v0.1.22
-git tag -f pex-v0.1 v0.1.22
-git tag -f v0.1.27 v0.1
-
-# needs a force push to move remote tags
-git push -f origin v0.1
-git push -f origin pex-v0.1
-git push -f origin v0.1.27
-```
-
-Note: both `v0.1` and `pex-v0.1` tags should be kept in sync.
-
-# Step 7. Merge the release branch into main
-
-Create a PR, get approval, merge.
-
-# Step 8. (optional) Revert
-
-To revert, just tag the previous point version with the live tag and re push
-
-```bash
-git tag -f v0.1 v0.1.21
-git tag -f pex-v0.1 v0.1.21
-git push -f origin v0.1
-git push -f origin pex-v0.1
-```
-
 # Development and testing
 
 ## Testing the dagster-cloud.pex against a Dagster development branch

actions/utils/copy_template/action.yml

@@ -12,5 +12,5 @@ inputs:
     description: "A string of the base image name for the deployed code location image."
 runs:
   using: "docker"
-  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:0.1.43"
+  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:dev"
   entrypoint: "/copy_template.sh"

actions/utils/deploy/action.yml

@@ -39,7 +39,7 @@ outputs:
     description: "The Cloud deployment associated with this branch."
 runs:
   using: "docker"
-  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:0.1.43"
+  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:dev"
   entrypoint: "/deploy.sh"
   args:
     - ${{ inputs.pr }}

actions/utils/get_branch_deployment/action.yml

@@ -15,5 +15,5 @@ outputs:
     description: "The Cloud deployment associated with this branch."
 runs:
   using: "docker"
-  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:0.1.43"
+  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:dev"
   entrypoint: "/get_branch_deployment.sh"

actions/utils/notify/action.yml

@@ -30,7 +30,7 @@ inputs:
 
 runs:
   using: "docker"
-  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:0.1.43"
+  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:dev"
   entrypoint: "/notify.sh"
   args:
     - ${{ inputs.pr }}

actions/utils/registry_info/action.yml

@@ -12,5 +12,5 @@ inputs:
     description: "Alternative to providing organization ID. The URL of your Dagster Cloud organization."
 runs:
   using: "docker"
-  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:0.1.43"
+  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:dev"
   entrypoint: "/registry_info.sh"

actions/utils/run/action.yml

@@ -35,7 +35,7 @@ outputs:
     description: "The ID of the launched run."
 runs:
   using: "docker"
-  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:0.1.43"
+  image: "docker://ghcr.io/dagster-io/dagster-cloud-action:dev"
   entrypoint: "/run.sh"
   args:
     - ${{ inputs.pr }}

generated/gha/dagster-cloud.pex

@@ -12,7 +12,7 @@ deploy-branch:
   stage: deploy
   rules:
     - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
-  image: ghcr.io/dagster-io/dagster-cloud-action:0.1.43
+  image: ghcr.io/dagster-io/dagster-cloud-action:dev
   script:
     # first create the branch deployment
     - export PR_TIMESTAMP=$(git log -1 --format='%cd' --date=unix)
@@ -51,7 +51,7 @@ deploy-branch:
 
 close_branch:
   stage: deploy
-  image: ghcr.io/dagster-io/dagster-cloud-action:0.1.43
+  image: ghcr.io/dagster-io/dagster-cloud-action:dev
   when: manual
   only:
     - merge_requests
@@ -76,7 +76,7 @@ deploy:
   stage: deploy
   rules:
     - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
-  image: ghcr.io/dagster-io/dagster-cloud-action:0.1.43
+  image: ghcr.io/dagster-io/dagster-cloud-action:dev
   script:
     # install dbt package
     - pip install pip --upgrade

gitlab/dbt/serverless-ci-dbt.yml

@@ -1,4 +1,4 @@
-# See https://docs.dagster.io/dagster-cloud/getting-started 
+# See https://docs.dagster.io/dagster-cloud/getting-started
 variables:
   # The organization name in Dagster Cloud
   DAGSTER_CLOUD_ORGANIZATION: <organinization-name>
@@ -29,11 +29,11 @@ workflow:
 
 initialize:
   stage: setup
-  image: ghcr.io/dagster-io/dagster-cloud-action:0.1.43
+  image: ghcr.io/dagster-io/dagster-cloud-action:dev
   script:
     - export
     - dagster-cloud ci check --project-dir=$DAGSTER_PROJECT_DIR --dagster-cloud-yaml-path=$DAGSTER_CLOUD_YAML_PATH
-    - > 
+    - >
       dagster-cloud ci init --deployment=prod --statedir=$DAGSTER_BUILD_STATEDIR
       --project-dir=$DAGSTER_PROJECT_DIR --dagster-cloud-yaml-path=$DAGSTER_CLOUD_YAML_PATH
       --git-url=$CI_PROJECT_URL/-/commit/$CI_COMMIT_SHA
@@ -75,7 +75,7 @@ deploy-docker:
   dependencies:
     - build-image
     - initialize
-  image: ghcr.io/dagster-io/dagster-cloud-action:0.1.43
+  image: ghcr.io/dagster-io/dagster-cloud-action:dev
   script:
     - dagster-cloud ci set-build-output --image-tag=$IMAGE_TAG
     - dagster-cloud ci deploy
@@ -87,7 +87,7 @@ deploy-docker-branch:
   dependencies:
     - build-image
     - initialize
-  image: ghcr.io/dagster-io/dagster-cloud-action:0.1.43
+  image: ghcr.io/dagster-io/dagster-cloud-action:dev
   script:
     - dagster-cloud ci set-build-output --image-tag=$IMAGE_TAG
     - dagster-cloud ci deploy
@@ -97,7 +97,7 @@ deploy-docker-branch:
 
 close-branch:
   stage: deploy
-  image: ghcr.io/dagster-io/dagster-cloud-action:0.1.43
+  image: ghcr.io/dagster-io/dagster-cloud-action:dev
   when: manual
   only:
     - merge_requests