Skip to content

fix(phishingprotection): use correct release status #9451

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
Merged
merged 1 commit into from
Oct 10, 2019
Merged

fix(phishingprotection): use correct release status #9451

merged 1 commit into from
Oct 10, 2019

Conversation

tseaver
Copy link
Contributor

@tseaver tseaver commented Oct 10, 2019 •
edited
Loading

Should fix the b0rken release build from #9447.

@tseaver tseaver added packaging api: phishingprotection Issues related to the Phishing Protection API. labels Oct 10, 2019
@tseaver tseaver requested a review from busunkim96 October 10, 2019 22:10
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Oct 10, 2019
@tseaver tseaver merged commit 22c0782 into googleapis:master Oct 10, 2019
@tseaver tseaver deleted the phishingprotection-fix-release-status branch October 10, 2019 22:28
@tseaver tseaver mentioned this pull request Oct 10, 2019
Merged
parthea pushed a commit that referenced this pull request Jun 4, 2023
@tseaver
fix(phishingprotection): use correct release status (#9451)
e38ad76
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
1 more reviewer

@busunkim96 busunkim96 busunkim96 approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
api: phishingprotection Issues related to the Phishing Protection API. cla: yes This human has signed the Contributor License Agreement. packaging
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@tseaver @busunkim96 @googlebot