-
Notifications
You must be signed in to change notification settings - Fork 229
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
fix: tag releases before opening new pull requests #753
Conversation
🤖 I have created a release *beep* *boop* --- ## [3.7.8](google-github-actions/release-please-action@v3.7.7...v3.7.8) (2023-04-11) ### Bug Fixes * bump release-please from 15.9.2 to 15.10.2 ([#755](https://github.com/google-github-actions/release-please-action/issues/755)) ([6730d1a](google-github-actions/release-please-action@6730d1a)) * tag releases before opening new pull requests ([#753](https://github.com/google-github-actions/release-please-action/issues/753)) ([6a803df](google-github-actions/release-please-action@6a803df)), closes [#747](https://github.com/google-github-actions/release-please-action/issues/747) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
I believe this PR caused a regression. I've been trying to hunt down the cause of my issue for months, and originally posted about it here. I finally pinpointed it to this change, and was able to fix my deploys by locking the GH action version to v3.7.6. Effectively, all of my releases would fail with "Not Found". |
@Nickersoft i'm having this issue as well. I've tried granting all permissions to my PAT to no avail. The release-please does it's job; we just have this false-negatives. sigh Did you ever find a fix beyond pinning an older version? |
Fixes #747