Closed mrcjkb closed 2 weeks ago
Looks like it all started with this failed run, which was triggered by merging a release PR:
❯ pull request title pattern: undefined
✔ Looking for open release pull requests
✔ found 0 open release pull requests.
✔ Looking for snoozed release pull requests
✔ found 0 snoozed release pull requests.
❯ Fetching CHANGELOG.md from branch master
❯ Fetching version.txt from branch master
⚠ file version.txt did not exist
❯ Fetching .release-please-manifest.json from branch master
⚠ file .release-please-manifest.json did not exist
✔ Starting GitHub PR workflow...
✔ Successfully found branch HEAD sha "7a8665bdf891ec00277704fd4a5b719587ca9082".
✔ Successfully created branch at https://api.github.com/repos/mrcjkb/rustaceanvim/git/refs/heads/release-please--branches--master
✔ Got the latest commit tree
✔ Successfully created a tree with the desired changes with SHA 81ce15e967f99c3636dfd168e9c961e9414d0fec
✔ Successfully created commit. See commit at https://api.github.com/repos/mrcjkb/rustaceanvim/git/commits/c140bbaaba678b803b8f186bce2248fd889be217
✔ Updating reference heads/release-please--branches--master to c140bbaaba678b803b8f186bce2248fd889be217
✔ Successfully updated reference release-please--branches--master to c140bbaaba678b803b8f186bce2248fd889be217
Error: release-please failed: Server Error
Manually pushing the tag and creating a release for the failed run has fixed the issue.
Hey :wave:
I had the release-please action configured to bootstrap at a given commit (via a
release-please-config.json
. It all worked fine, until a few days ago, the workflow runs started adding the entire commit history to the latest release (ignoring the bootstrap sha and the last release), resulting in this PR generated by this workflow run.I have tried