fixes

Author: andreaangiolillo

.github/scripts/get_list_files_to_delete.sh

@@ -44,7 +44,7 @@ done
 
 # Display the files marked for deletion
 if [ ${#files_to_delete[@]} -gt 0 ]; then
-  echo "V2_OPEN_API_FILES_TO_DELETE=${files_to_delete[*]}" >> "${GITHUB_ENV:?}"
+  echo "V2_OPEN_API_FILES_TO_DELETE=${files_to_delete[*]}" >> "${GITHUB_OUTPUT:?}"
   for file_to_del in "${files_to_delete[@]}"; do
     echo "${file_to_del}"
   done

.github/workflows/release-cleanup.yml

@@ -65,18 +65,20 @@ jobs:
         if: env.FILES_CHANGED == 'true'
         with:
           token: ${{ secrets.api_bot_pat }}
-          title: "APIBot: Release Cleanup"
+          title: "APIx-Bot: Release Cleanup 🧹🍃"
           commit-message: "release cleanup"
           delete-branch: true
           branch: release-cleanup-${{ github.run_id }}
-          body: |              
-              > NOTE: This PR is autogenerated.
-              > DO NOT MERGE THE PR IF YOU ARE UNSURE ABOUT THE CHANGE.
-              
-              # Description
-              This PR deletes files related to an "Upcoming" api that has been released to a "Stable" API.
-              
-              ## Why?
-              The MongoDB Admin API renders OpenAPI specifications and changelog files from this repository. 
-              Since this API version is now “Stable,” the files corresponding to its previous “Upcoming” state are obsolete.
-              Deleting these files prevents the Admin API from inadvertently displaying outdated or irrelevant information from these older specifications and changelogs.
+          add-paths: |
+            openapi/v2/*
+          body: |
+            > NOTE: This PR is autogenerated.
+            > DO NOT MERGE THE PR IF YOU ARE UNSURE ABOUT THE CHANGE.
+            
+            # Description
+            This PR deletes files related to an `Upcoming` api that has been released to a `Stable` API.
+            
+            ## Why?
+            The MongoDB Admin API renders OpenAPI specifications and changelog files from this repository. 
+            Since this API version is now `Stable`, the files corresponding to its previous `Upcoming` state are obsolete.
+            Deleting these files prevents the Admin API from inadvertently displaying outdated or irrelevant information from these older specifications and changelogs.