Error: Request body length does not match content-length header

[qwerttvv]

    - name: Upload firmware to release
      uses: softprops/action-gh-release@master
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      with:
        tag_name: ${{ steps.tag.outputs.release_tag }}
        body_path: release.txt
        files: ${{ env.FIRMWARE }}/*

full yml
https://github.com/qwerttvv/Router/blob/master/.github/workflows/M2-VIKINGYFY.yml

log

👩‍🏭 Creating new GitHub release for tag 2024.12.11-22.51_M2-VIKINGYFY...
⬆️ Uploading version.buildinfo...
⬆️ Uploading sha256sums...
⬆️ Uploading profiles.json...
⬆️ Uploading immortalwrt-qualcommax-ipq60xx-cmiot_ax18.manifest...
⬆️ Uploading immortalwrt-qualcommax-ipq60xx-cmiot_ax18-squashfs-sysupgrade.bin...
⬆️ Uploading immortalwrt-qualcommax-ipq60xx-cmiot_ax18-squashfs-factory.ubi...
⬆️ Uploading immortalwrt-qualcommax-ipq60xx-cmiot_ax18-initramfs-uImage.itb...
⬆️ Uploading feeds.buildinfo...
⬆️ Uploading config.buildinfo...
Error: Request body length does not match content-length header

good ver-last week
https://github.com/softprops/action-gh-release/tree/92bc83c4214f780e84c7d2a85464a2ca05ebc2f0

not good ver-nowsoftprops/action-gh-release@master
https://github.com/softprops/action-gh-release/tree/7b4da11513bf3f43f9999e90eabced41ab8bb048

[gtxaspec]

confirmed, the latest commits produce this error.

[wanansany]

Don't use master，use v2
uses: softprops/action-gh-release@v2

[qwerttvv]

#555 smae issue

[VietND96]

Don't use master，use v2 uses: softprops/action-gh-release@v2

The same goes for me.
I saw the latest commit on master is releasing v2.2.0, so I am wondering why softprops/action-gh-release@v2 is able to work?

[qwerttvv]

Don't use master，use v2 uses: softprops/action-gh-release@v2

The same goes for me. I saw the latest commit on master is releasing v2.2.0, so I am wondering why softprops/action-gh-release@v2 is able to work?

now, v2=v2.0.9
see this https://github.com/softprops/action-gh-release/tags

[VietND96]

Thanks for pointing. I assumed it always points to the latest, but need the author to bump it.

[brunoalr]

Also happened to me https://github.com/OpenImageDebugger/OpenImageDebugger/actions/runs/12288435680/job/34394129310

[c2tz]

hello, i'll stick with v2 for now

[clintonsteiner]

64f1fa1
Believe related to this one

[gtxaspec]

FYI @xen0n @chenrui333

[clintonsteiner]

https://github.com/jenkinsci/jenkins/actions/runs/12416637271

Heres a run illustrating the behavior,

[clintonsteiner]

Error: Request body length does not match content-length header

[xen0n]

Hmm, I will look into this.

[clintonsteiner]

@xen0n since so many others have confirmed the same issue and are rolling back.

Can we instead revert back to commits at 2.1.0, and rerelease it?

Thinking this package will end up forgotten about and never updated should too many repos commit locks for python 2.10

[xen0n]

@xen0n since so many others have confirmed the same issue and are rolling back.

Can we instead revert back to commits at 2.1.0, and rerelease it?

Thinking this package will end up forgotten about and never updated should too many repos commit locks for python 2.10

I don't have the permissions to make a release, so this would have to be done by @chenrui333 .

Temporary workaround:

- uses: softprops/[email protected]