Doug Tangren

> But why the createRelease returns 404 A 404 can happen for different reasons. In a future release Im going to include more debugging information from api response headers the...

It’s still and issue as far as I know looking into it in https://github.com/softprops/action-gh-release/pull/145

Deep apologies for the disruption and thas for the reports folks. Keep the links coming where possible. until I’m able to get a deeper understanding of the problem the suggested...

> the new and improved goes to a v2 tag This is a good idea and I feel you but I’d like to reserve these for intentional breaking changes. We...

> it would probably be better to make the discussions category optional again Hrm. It shouldn’t be required today https://github.com/softprops/action-gh-release/blob/815e45857946b196197a116aa0def711ff7f8ecc/action.yml#L42 This should be easy to fix if not

the main issue the causing the error breaking releases is now fixed in https://github.com/softprops/action-gh-release/releases/tag/v0.1.12 (v1 tag was updated) there may be smaller cosmetic issues but the main issue is resolved

the tl'dr on the underlying issue. post the [introduction of target_commitish](https://github.com/softprops/action-gh-release/pull/76) users not using the new input were impacted in this way 1. attempt to resolve an release to update...

@CalvinWilkinson You can use these https://github.com/softprops/action-gh-release/issues/139#issuecomment-895714781

This is likely the same error reported in https://github.com/softprops/action-gh-release/issues/139

> caused the interesting side-effect of inlining the body_path.txt file 3 times. I think I can see that regression in this pull request https://github.com/softprops/action-gh-release/pull/109/files#diff-a248ff5ec76368168c745273fee0601b243545fdca37aa3bec76ef9e9365fdb7R189 Can you open a specific issue...