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.

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

Upgrade version.error-prone-orig 2.20.0 -> 2.21.0 #737

Merged
merged 2 commits into from
Aug 3, 2023

Conversation

Picnic-Bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
com.google.errorprone:error_prone_annotations (source) compile minor 2.20.0 -> 2.21.0
com.google.errorprone:error_prone_core (source) minor 2.20.0 -> 2.21.0
com.google.errorprone:error_prone_test_helpers (source) compile minor 2.20.0 -> 2.21.0
com.google.errorprone:error_prone_core (source) compile minor 2.20.0 -> 2.21.0
com.google.errorprone:error_prone_check_api (source) compile minor 2.20.0 -> 2.21.0
com.google.errorprone:error_prone_annotation (source) compile minor 2.20.0 -> 2.21.0

Release Notes

google/error-prone (com.google.errorprone:error_prone_annotations)

v2.21.0: Error Prone 2.21.0

Compare Source

New Checkers:

Fixed issues: #​3976, #​3986, #​4001, #​4002, #​4026, #​4027

Full Changelog: google/error-prone@v2.20.0...v2.21.0


  • If you want to rebase/retry this PR, check this box

@Picnic-Bot
Copy link
Contributor Author

Picnic-Bot commented Aug 2, 2023

Warning
Renovate's suggested commit message is being replaced with improved initial commits to enable automerging. As a side effect, these suggested commit messages might have changed. Consider comparing the initial commit message and this message to determine the most suitable one. Please leave feedback in #sys-renovate.

Suggested commit message:

Upgrade Error Prone 2.20.0 -> 2.21.0 (#737)

See:
- https://github.com/google/error-prone/releases/tag/v2.21.0
- https://github.com/google/error-prone/compare/v2.20.0...v2.21.0
- https://github.com/PicnicSupermarket/error-prone/compare/v2.20.0-picnic-1...v2.21.0-picnic-1

@github-actions
Copy link

github-actions bot commented Aug 2, 2023

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

2 similar comments
@github-actions
Copy link

github-actions bot commented Aug 2, 2023

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@github-actions
Copy link

github-actions bot commented Aug 2, 2023

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a commit to this branch, but it does not yet show up in this PR view. Approving, assuming that later it does, and that the subsequently triggered build passes.

Also updated the suggested commit message.

(The NamedLikeContextualKeyword flag changes should have been part of the previous upgrade. There's overlap with (a.o.) Checkstyle, but enabling these flags can't hurt, I think.)

@Stephan202 Stephan202 closed this Aug 2, 2023
@Stephan202 Stephan202 reopened this Aug 2, 2023
@github-actions
Copy link

github-actions bot commented Aug 2, 2023

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

1 similar comment
@github-actions
Copy link

github-actions bot commented Aug 2, 2023

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@Stephan202 Stephan202 added this to the 0.13.0 milestone Aug 2, 2023
@Stephan202
Copy link
Member

Closing and re-opening the PR fixed it ✔️

@rickie rickie force-pushed the renovate/version.error-prone-orig branch from 6603e77 to 0d86472 Compare August 2, 2023 12:41
@github-actions
Copy link

github-actions bot commented Aug 2, 2023

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Member

@rickie rickie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes 😄.

@rickie
Copy link
Member

rickie commented Aug 2, 2023

Tweaked suggested commit message.

@Stephan202
Copy link
Member

Tnx!

@Picnic-Bot
Copy link
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@rickie rickie force-pushed the renovate/version.error-prone-orig branch from 0d86472 to ed38bfc Compare August 3, 2023 08:55
@rickie
Copy link
Member

rickie commented Aug 3, 2023

Will merge once 📗.

@github-actions
Copy link

github-actions bot commented Aug 3, 2023

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Aug 3, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@rickie rickie merged commit 8375f16 into master Aug 3, 2023
@rickie rickie deleted the renovate/version.error-prone-orig branch August 3, 2023 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants