releaser-pleaser/internal
Julian Tölle 9775cb8850 fix(github): duplicate release pr when process is stopped at wrong moment
In a timing issue, the release pull request may be created but the
releaser-pleaser labels not added. On the next run releaser-pleaser
then creates a second release pull request. We try to reduce the chance
of this happening by checking the context cancellation at the top, and
if its not cancelled we run both API requests without passing along any
cancellations from the parent context.

Closes #215
2025-08-23 22:58:46 +02:00
..
changelog feat: highlight breaking changes in release notes (#234) 2025-08-23 22:40:28 +02:00
commitparser fix: use commits with slightly invalid messages in release notes (#105) 2024-11-15 17:25:15 +01:00
forge fix(github): duplicate release pr when process is stopped at wrong moment 2025-08-23 22:58:46 +02:00
git refactor: let updaters define the files they want to run on (#233) 2025-08-23 22:14:34 +02:00
markdown feat: edit commit message after merging through PR (#43) 2024-09-06 23:17:06 +02:00
pointer refactor: move things to packages (#39) 2024-08-31 15:23:21 +02:00
releasepr chore: update golangci-lint to v2 and fix breakage (#184) 2025-06-07 16:39:18 +00:00
updater refactor: let updaters define the files they want to run on (#233) 2025-08-23 22:14:34 +02:00
versioning feat(github): mark pre-releases correctly (#110) 2024-11-15 18:49:50 +01:00