Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[java] erroneously opened a new snapshot release PR after merging a snapshot PR #1540

Closed
chingor13 opened this issue Aug 1, 2022 · 3 comments
Closed

[java] erroneously opened a new snapshot release PR after merging a snapshot PR #1540

chingor13 opened this issue Aug 1, 2022 · 3 comments
Assignees
@chingor13
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@chingor13
Copy link
Contributor

A snapshot bump PR was merged 2022-07-26 1:50pm PST. Release-Please then opened a new snapshot bump PR which was then re-used to become a new release. The caused the release to fail to be tagged because it was labeled incorrectly.

Somewhat related: #1352
@chingor13 chingor13 added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Aug 1, 2022
@kolea2
Copy link

kolea2 commented Aug 1, 2022

Some extra info for debugging - a new snapshot PR was still opened up after the release PR (labeled as snapshot) was merged googleapis/java-bigtable#1331

@tmatsuo
Copy link
Contributor

tmatsuo commented Oct 4, 2022

Do we have a repro, or hypothesis of repro?

@chingor13
Copy link
Contributor Author

This seems to be exceedingly rare. closing until it happens again and we have logs

@chingor13 chingor13 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chingor13 chingor13

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chingor13 @tmatsuo @kolea2