github/release: Update Slack channel reference (#347)

radeksimko · web-flow · commit 08dbb4f5d088 · 2026-02-16T10:26:49.000Z
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -38,7 +38,7 @@ jobs:
             --environment=hc-install-oss \
             --org=hashicorp \
             --repo=hc-install \
-            --slack-channel=C01QDH3Q37W \
+            --slack-channel=C09KZFQ52CS \
             --product-version=$VERSION \
             --sha=$SHA \
             --branch=$BRANCH \
@@ -66,7 +66,7 @@ jobs:
             --environment=hc-install-oss \
             --org=hashicorp \
             --repo=hc-install \
-            --slack-channel=C01QDH3Q37W \
+            --slack-channel=C09KZFQ52CS \
             --product-version=$VERSION \
             --sha=$SHA \
             --branch=$BRANCH \
diff --git a/.release/ci.hcl b/.release/ci.hcl
@@ -8,7 +8,7 @@ project "hc-install" {
   // but is required to be non-empty by CRT orchestrator
   team = "_UNUSED_"
   slack {
-    notification_channel = "C01QDH3Q37W" // #feed-terraform-exec
+    notification_channel = "C09KZFQ52CS" // #feed-terraform-exec
   }
   github {
     organization     = "hashicorp"
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
@@ -13,7 +13,7 @@ Release process:
    - This will kick off staging and then production promotions. However, there is currently no way of blocking the production promotion until (staging) artifacts are in place, so **the production promotion is likely to fail**.
 1. Wait for [`promote-staging` workflow](https://github.com/hashicorp/crt-workflows-common/actions/workflows/crt-promote-staging.yml) to finish.
 1. Retry the failed `production` job of the `release` workflow
-1. Wait for a message [in the Slack channel](https://hashicorp.enterprise.slack.com/archives/C01QDH3Q37W) saying that authorisation is needed to promote artifacts to production. Click on the link and approve.
+1. Wait for a message [in the Slack channel](https://ibm.enterprise.slack.com/archives/C09KZFQ52CS) saying that authorisation is needed to promote artifacts to production. Click on the link and approve.
 1. Wait for the [`promote-production` workflow](https://github.com/hashicorp/crt-workflows-common/actions/workflows/crt-promote-production.yml) to finish
 1. Click on the pencil icon of [the latest release](https://github.com/hashicorp/hc-install/releases), click `Generate release notes`, make any manual changes if necessary (e.g. to call out any breaking changes) and `Update release`.
 1. Update [`version/VERSION`](https://github.com/hashicorp/hc-install/blob/main/version/VERSION) and add `-dev` suffix and set it to the expected next version to be released

Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,7 @@ project "hc-install" {`
`8`	`8`	`// but is required to be non-empty by CRT orchestrator`
`9`	`9`	`team = "_UNUSED_"`
`10`	`10`	`slack {`
`11`		`- notification_channel = "C01QDH3Q37W" // #feed-terraform-exec`
	`11`	`+ notification_channel = "C09KZFQ52CS" // #feed-terraform-exec`
`12`	`12`	`}`
`13`	`13`	`github {`
`14`	`14`	`organization = "hashicorp"`