chore(deps): update dependency com.lightbend.akka.grpc:sbt-akka-grpc to v2.3.0

renovate[bot] commented 2 years ago

This PR contains the following updates:

Package	Type	Update	Change
com.lightbend.akka.grpc:sbt-akka-grpc (source)	plugin	minor	`2.1.6` -> `2.3.0`

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

Release Notes

akka/akka-grpc

### [`v2.3.0`](https://togithub.com/akka/akka-grpc/releases/tag/v2.3.0): Akka gRPC 2.3.0 [Compare Source](https://togithub.com/akka/akka-grpc/compare/v2.2.1...v2.3.0) ##### What's Changed This release of Akka gRPC depends on Akka HTTP 10.5.0 - Native Scala3 artefacts by [@johanandren](https://togithub.com/johanandren) in [https://github.com/akka/akka-grpc/pull/1710](https://togithub.com/akka/akka-grpc/pull/1710) - Send transitive dependencies in server reflection by [@jroper](https://togithub.com/jroper) in [https://github.com/akka/akka-grpc/pull/1719](https://togithub.com/akka/akka-grpc/pull/1719) - Rich error model client api by [@raboof](https://togithub.com/raboof) in [https://github.com/akka/akka-grpc/pull/1665](https://togithub.com/akka/akka-grpc/pull/1665) - Better names for rich status metadata, better details lookup API by [@johanandren](https://togithub.com/johanandren) in [https://github.com/akka/akka-grpc/pull/1740](https://togithub.com/akka/akka-grpc/pull/1740) - Don't log peer closing connection at error by [@johanandren](https://togithub.com/johanandren) in [https://github.com/akka/akka-grpc/pull/1745](https://togithub.com/akka/akka-grpc/pull/1745) - Include information about called service in StatusRuntimeException by [@johanandren](https://togithub.com/johanandren) in [https://github.com/akka/akka-grpc/pull/1748](https://togithub.com/akka/akka-grpc/pull/1748) ##### Dependency updates - bump: Protoc 3.21.9 by [@johanandren](https://togithub.com/johanandren) in [https://github.com/akka/akka-grpc/pull/1720](https://togithub.com/akka/akka-grpc/pull/1720) - bump: Scala XML 2.1.0 across the modules by [@johanandren](https://togithub.com/johanandren) in [https://github.com/akka/akka-grpc/pull/1736](https://togithub.com/akka/akka-grpc/pull/1736) - note that this may require you to bump other sbt plugins like sbt-native-packager to recent versions as well - bump: maven-core, maven-plugin-api 3.9.0 (was 3.8.7) by [@scala-steward](https://togithub.com/scala-steward) in [https://github.com/akka/akka-grpc/pull/1751](https://togithub.com/akka/akka-grpc/pull/1751) **Full Changelog**: https://github.com/akka/akka-grpc/compare/v2.2.1...v2.3.0 ### [`v2.2.1`](https://togithub.com/akka/akka-grpc/releases/tag/v2.2.1) [Compare Source](https://togithub.com/akka/akka-grpc/compare/v2.2.0...v2.2.1) ##### What's Changed - bump: Protoc 3.21.9 [#1720](https://togithub.com/akka/akka-grpc/pull/1720) with fix for [CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) **Full Changelog**: https://github.com/akka/akka-grpc/compare/v2.2.0...v2.2.1 ### [`v2.2.0`](https://togithub.com/akka/akka-grpc/releases/tag/v2.2.0): Akka gRPC 2.2.0 [Compare Source](https://togithub.com/akka/akka-grpc/compare/v2.1.6...v2.2.0) ##### Changes - nowarn for never used different for 2.12 vs 2.13 [#1699](https://togithub.com/akka/akka-grpc/issues/1699) by [@patriknw](https://togithub.com/patriknw) - akka-grpc-codegen published twice [#1696](https://togithub.com/akka/akka-grpc/issues/1696) by [@patriknw](https://togithub.com/patriknw) - Scheduled Fossa validation [#1685](https://togithub.com/akka/akka-grpc/issues/1685) by [@patriknw](https://togithub.com/patriknw) - Change license [#1678](https://togithub.com/akka/akka-grpc/issues/1678) by [@patriknw](https://togithub.com/patriknw) ##### sbt - Update to Akka 2.7.0, Akka HTTP 10.4.0 [#1702](https://togithub.com/akka/akka-grpc/issues/1702) by [@patriknw](https://togithub.com/patriknw) ##### Updates - Update to Akka 2.7.0, Akka HTTP 10.4.0 [#1702](https://togithub.com/akka/akka-grpc/issues/1702) by [@patriknw](https://togithub.com/patriknw) - Scala 2.12.17 & 2.13.10 [#1694](https://togithub.com/akka/akka-grpc/issues/1694) by [@patriknw](https://togithub.com/patriknw) - Update Paradox [#1687](https://togithub.com/akka/akka-grpc/issues/1687) by [@patriknw](https://togithub.com/patriknw)

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Mend Renovate. View repository job log here.

sonarcloud[bot] commented 2 years ago

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

xuwei-k commented 2 years ago

sonarcloud[bot] commented 1 year ago

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

github-actions[bot] commented 1 year ago

Stale pull request message

pull-request-quantifier-deprecated[bot] commented 1 year ago

This PR has 2 quantified lines of changes. In general, a change size of upto 999 lines is ideal for the best PR experience!

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 2% Total files changed: 1 Change summary by file extension: .sbt : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup: :ok_hand: :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

sonarcloud[bot] commented 1 year ago

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

worxbend / sandbox