diff --git a/.gitea/workflows/check_releases.yaml b/.gitea/workflows/check_releases.yaml
index de19867..8d8390d 100644
--- a/.gitea/workflows/check_releases.yaml
+++ b/.gitea/workflows/check_releases.yaml
@@ -36,17 +36,6 @@ jobs:
 
           echo "✅ Found latest version: ${LATEST_TAG} published on ${PUBLISH_DATE}"
 
-          # # --- 2. Implement your custom logic here ---
-          # # You need a mechanism to store the previously checked tag/date
-          # # For simplicity, we will just check if we found ANY release data.
-
-          # # Example Logic: If you want to perform an action ONLY IF the date is new...
-          # # (In a real scenario, you would compare $PUBLISH_DATE against a stored variable)
-
-          # echo "Successfully retrieved version data."
-          # # echo "LATEST_VERSION=${LATEST_TAG}" >> $GITHUB_ENV
-          # echo "LATEST_VERSION=${LATEST_TAG}"
-
       - name: Download latest release
         run: |
           DOWNLOAD_URL="https://github.com/prefix-dev/pixi/releases/download/v${LATEST_TAG}/pixi-x86_64-unknown-linux-musl.tar.gz"
@@ -56,11 +45,3 @@ jobs:
           curl -L -o pixi-latest.tar.gz "$DOWNLOAD_URL"
           tar xfvz pixi-latest.tar.gz
           ls -la .
-
-          # curl -L -o latest
-
-      # - name: Deploy/Build action if release found
-      #   if: env.LATEST_VERSION # This step runs ONLY if the previous step successfully set LATEST_VERSION
-      #   run: |
-      #     echo "🚀 A new major version ($LATEST_VERSION) has been released! Initiating build/deploy..."
-      #     # Add your deployment steps here (e.g., upload artifact, trigger CI job)