[BUG] Firebase Hosting GitHub Action fails with "supplied version is the current active version" but changes are still deployed

I'm using the FirebaseExtended/action-hosting-deploy@v0 GitHub Action to deploy a Flutter web application to Firebase Hosting. Every time I push changes to my code, the action runs and fails with an HTTP 400 error. However, despite the failure, the new changes are actually reflected on the live production site.

Project type: Flutter web application (build output is in build/web).

Action used: FirebaseExtended/action-hosting-deploy@v0.

Firebase project ID: hotel-delivery-65492.

Trigger: The workflow runs on push to the main branch.

Local behavior: If I run firebase deploy --only hosting locally, it works perfectly without any errors.

part of my workflow file:
uses: FirebaseExtended/action-hosting-deploy@v0
with:
repoToken: ${{ secrets.GITHUB_TOKEN }}
firebaseServiceAccount: ${{ secrets.FIREBASE_SERVICE_ACCOUNT_HOTEL_DELIVERY_65492 }}
channelId: live
projectId: hotel-delivery-65492

Error:
Request to https://firebasehosting.googleapis.com/v1beta1/projects/-/sites/app-teste-65492/channels/live/releases?versionName=projects%2F43565238095%2Fsites%2Fapp-teste-65492%2Fversions%2Fffg60o2a0014032323 had HTTP Error: 400, Can't release to projects/-/sites/app-teste-65492/channels/live: supplied version projects/43065038795/sites/app-teste-65492/versions/ffg632a044032123 is the current active version.

Start with the workflow entry point using FirebaseExtended/action-hosting-deploy@v0, compare its live-channel release behavior with a local firebase deploy --only hosting, and check the build/web deployment context. Done means pushes to main deploy the changed Flutter web output and the action completes without the HTTP 400 current-active-version error.

Written by the indexing model from the issue text.