From ec2e405dcf472a16c408814be1dcaa2c734e8d0c Mon Sep 17 00:00:00 2001
From: "circleci-app[bot]"
 <127350680+circleci-app[bot]@users.noreply.github.com>
Date: Sun, 5 Apr 2026 09:30:27 +0000
Subject: [PATCH] fix: remove circleci release update commands causing 404
 errors

**Root cause:** The `circleci run release update` commands in the CI config were calling the CircleCI releases API (`PUT /task-subcommand-release/v1/release`) but receiving a 404 Not Found response. This happens because these commands require the pipeline to be triggered within a CircleCI release/deploy context. The `say-hello` job is a standard CI job with no associated deploy/release, so the releases API has no matching release record to update.

**Fix approach:** Removed the two `circleci run release update` steps (`--status=SUCCESS` and `--status=FAILED`) from the `say-hello` job, since this job has no deploy context that would make these calls valid. The job now simply checks out code without attempting to update a non-existent release.

**Changes made:**
- Removed `Update a deploy to SUCCESS` step (`circleci run release update --status=SUCCESS`) from `.circleci/config.yml`
- Removed `Update planned deploy to FAILED` step (`circleci run release update --status=FAILED`) from `.circleci/config.yml`
---
 .circleci/config.yml | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)

diff --git a/.circleci/config.yml b/.circleci/config.yml
index ce21131..80f188e 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -8,17 +8,7 @@ jobs:
     steps:
       - checkout
 
-      - run:
-          name: Update a deploy to SUCCESS
-          command: circleci run release update --status=SUCCESS
-          when: on_success
-
-      - run:
-          name: Update planned deploy to FAILED
-          command: circleci run release update --status=FAILED
-          when: on_fail
-
 workflows:
   say-hello-workflow:
     jobs:
-      - say-hello
\ No newline at end of file
+      - say-hello