-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
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
Wrong release version on a failed GitHub API call #577
Comments
This sounds like the same issue for googleapis/release-please#1567 which is in 13.21.0 of the underlying release-please library. The cause is that GitHub graphql has been getting flakier and we were silently catching errors for fetching the list of recent commits (which means that release-please couldn't find the latest release). Retrying was the workaround. I've been having issues releasing the next version of the action, but it should be resolved today. |
This should be fixed now in 3.4.0 |
@chingor13 ❤️ |
I am having a similar issue where my current version is 0.4.0 but release-please is creating a PR for version 0.2.0. Logs:
And my YAML looks like this:
Any suggestions? This was working till very recently. A few more things:
Not sure if any of these could be causing issues. |
TL;DR
Release-please tried to bump one of our projects from 3.2.0 to 1.0.0. The action log shows a failed call to
pullRequestsSince
.The action got the version wrong and included a series of already released commits in the pull request.
Re-running the action fixed the pull request however, I think that bumping to 1.0.0 is not an optimal fallback solution.
I've attached the log output with more details.
Thank you,
Gildo
Expected behavior
No response
Observed behavior
No response
Action YAML
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: