We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The release failed due to the bug of softprops/action-gh-release.
Run softprops/action-gh-release@7b4da11513bf3f43f9999e90eabced41ab8bb048 👩🏭 Creating new GitHub release for tag v24.13.0... ⬆️ Uploading version.txt... ⬆️ Uploading themes.zip... ⬆️ Uploading posh-windows-arm64.exe... ⬆️ Uploading posh-windows-amd64.exe... ⬆️ Uploading posh-windows-386.exe... ⬆️ Uploading posh-linux-arm64... ⬆️ Uploading posh-linux-arm... ⬆️ Uploading posh-linux-amd64... ⬆️ Uploading posh-linux-386... ⬆️ Uploading posh-freebsd-arm64... ⬆️ Uploading posh-freebsd-arm... ⬆️ Uploading posh-freebsd-amd64... ⬆️ Uploading posh-freebsd-386... ⬆️ Uploading posh-darwin-arm64... ⬆️ Uploading posh-darwin-amd64... ⬆️ Uploading install-x86.msi.sha256... ⬆️ Uploading install-x86.msi... ⬆️ Uploading install-x64.msi.sha256... ⬆️ Uploading install-x64.msi... ⬆️ Uploading install-arm64.msi.sha256... ⬆️ Uploading install-arm64.msi... ⬆️ Uploading checksums.txt.sig... ⬆️ Uploading checksums.txt... Error: Request body length does not match content-length header
softprops/action-gh-release v2.2.0 has a known issue.
It was updated by Dependabot.
.
No response
The text was updated successfully, but these errors were encountered:
I created a pull request to resolve this issue.
Sorry, something went wrong.
JanDeDobbeleer
Successfully merging a pull request may close this issue.
Code of Conduct
What happened?
The release failed due to the bug of softprops/action-gh-release.
softprops/action-gh-release v2.2.0 has a known issue.
It was updated by Dependabot.
Theme
.
What OS are you seeing the problem on?
No response
Which shell are you using?
No response
Log output
.
The text was updated successfully, but these errors were encountered: