search

limpid-kzonix / data-engineering

Some random stuff with Kafka, KafkaConnect and Apache Flink
1 stars 0 forks source link

chore: Configure Renovate #2

Closed renovate[bot] closed 3 months ago

renovate[bot] commented 9 months ago

Mend Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

Configuration Summary

Based on the default config's presets, Renovate will:

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

What to Expect

With your current configuration, Renovate will create 14 Pull Requests:

fix(deps): update dependency io.confluent:kafka-connect-storage-partitioner to v11.2.16 - Schedule: ["at any time"] - Branch name: `renovate/io.confluent-kafka-connect-storage-partitioner-11.x` - Merge into: `main` - Upgrade [io.confluent:kafka-connect-storage-partitioner](https://togithub.com/confluentinc/kafka-connect-storage-common) to `11.2.16`
chore(deps): update dependency com.eed3si9n:sbt-assembly to v2.2.0 - Schedule: ["at any time"] - Branch name: `renovate/com.eed3si9n-sbt-assembly-2.x` - Merge into: `main` - Upgrade [com.eed3si9n:sbt-assembly](https://togithub.com/sbt/sbt-assembly) to `2.2.0`
chore(deps): update dependency org.apache.flink:flink-connector-kafka to v3.2.0-1.19 - Schedule: ["at any time"] - Branch name: `renovate/org.apache.flink-flink-connector-kafka-3.x` - Merge into: `main` - Upgrade org.apache.flink:flink-connector-kafka to `3.2.0-1.19`
chore(deps): update dependency org.apache.kafka:kafka-clients to v3.8.0 - Schedule: ["at any time"] - Branch name: `renovate/org.apache.kafka-kafka-clients-3.x` - Merge into: `main` - Upgrade org.apache.kafka:kafka-clients to `3.8.0`
chore(deps): update dependency org.apache.logging.log4j:log4j-api to v2.23.1 - Schedule: ["at any time"] - Branch name: `renovate/org.apache.logging.log4j-log4j-api-2.x` - Merge into: `main` - Upgrade org.apache.logging.log4j:log4j-api to `2.23.1`
chore(deps): update dependency org.apache.logging.log4j:log4j-core to v2.23.1 - Schedule: ["at any time"] - Branch name: `renovate/org.apache.logging.log4j-log4j-core-2.x` - Merge into: `main` - Upgrade org.apache.logging.log4j:log4j-core to `2.23.1`
chore(deps): update dependency org.apache.logging.log4j:log4j-slf4j-impl to v2.23.1 - Schedule: ["at any time"] - Branch name: `renovate/org.apache.logging.log4j-log4j-slf4j-impl-2.x` - Merge into: `main` - Upgrade org.apache.logging.log4j:log4j-slf4j-impl to `2.23.1`
chore(deps): update dependency sbt/sbt to v1.10.1 - Schedule: ["at any time"] - Branch name: `renovate/sbt-sbt-1.x` - Merge into: `main` - Upgrade [sbt/sbt](https://togithub.com/sbt/sbt) to `1.10.1`
chore(deps): update dependency scala to v2.13.14 - Schedule: ["at any time"] - Branch name: `renovate/scala-2.x` - Merge into: `main` - Upgrade [scala](https://togithub.com/scala/scala) to `2.13.14`
chore(deps): update flinkversion to v1.20.0 - Schedule: ["at any time"] - Branch name: `renovate/flinkversion` - Merge into: `main` - Upgrade org.apache.flink:flink-azure-fs-hadoop to `1.20.0` - Upgrade org.apache.flink:flink-clients to `1.20.0` - Upgrade org.apache.flink:flink-connector-base to `1.20.0` - Upgrade org.apache.flink:flink-json to `1.20.0` - Upgrade org.apache.flink:flink-s3-fs-hadoop to `1.20.0` - Upgrade org.apache.flink:flink-scala to `1.20.0` - Upgrade org.apache.flink:flink-statebackend-changelog to `1.20.0` - Upgrade org.apache.flink:flink-statebackend-heap-spillable to `1.20.0` - Upgrade org.apache.flink:flink-statebackend-rocksdb to `1.20.0` - Upgrade org.apache.flink:flink-streaming-java to `1.20.0` - Upgrade org.apache.flink:flink-streaming-scala to `1.20.0` - Upgrade org.apache.flink:flink-table-api-java to `1.20.0` - Upgrade org.apache.flink:flink-table-api-java-bridge to `1.20.0` - Upgrade org.apache.flink:flink-table-common to `1.20.0` - Upgrade org.apache.flink:flink-table-planner-loader to `1.20.0` - Upgrade org.apache.flink:flink-table-runtime to `1.20.0` - Upgrade org.apache.flink:flink-walkthrough-common to `1.20.0`
fix(deps): update dependency com.google.code.gson:gson to v2.11.0 - Schedule: ["at any time"] - Branch name: `renovate/com.google.code.gson-gson-2.x` - Merge into: `main` - Upgrade [com.google.code.gson:gson](https://togithub.com/google/gson) to `2.11.0`
fix(deps): update dependency org.apache.kafka:connect-api to v3.8.0 - Schedule: ["at any time"] - Branch name: `renovate/org.apache.kafka-connect-api-3.x` - Merge into: `main` - Upgrade org.apache.kafka:connect-api to `3.8.0`
chore(deps): update dependency scalafmt to v3 - Schedule: ["at any time"] - Branch name: `renovate/scalafmt-3.x` - Merge into: `main` - Upgrade [scalafmt](https://togithub.com/scalameta/scalafmt) to `3.8.3`
fix(deps): update dependency org.apache.kafka:connect-api to v7 - Schedule: ["at any time"] - Branch name: `renovate/org.apache.kafka-connect-api-7.x` - Merge into: `main` - Upgrade org.apache.kafka:connect-api to `7.7.0-ce`

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR was generated by Mend Renovate. View the repository job log.

pull-request-quantifier-deprecated[bot] commented 9 months ago

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

Quantification details

``` Label : Extra Small Size : +4 -0 Percentile : 1.6% Total files changed: 1 Change summary by file extension: .json : +4 -0 ``` > 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.

pull-request-quantifier-deprecated[bot] commented 9 months ago

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

Quantification details

``` Label : Extra Small Size : +4 -0 Percentile : 1.6% Total files changed: 1 Change summary by file extension: .json : +4 -0 ``` > 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.

pull-request-quantifier-deprecated[bot] commented 8 months ago

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

Quantification details

``` Label : Extra Small Size : +4 -0 Percentile : 1.6% Total files changed: 1 Change summary by file extension: .json : +4 -0 ``` > 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.

pull-request-quantifier-deprecated[bot] commented 8 months ago

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

Quantification details

``` Label : Extra Small Size : +4 -0 Percentile : 1.6% Total files changed: 1 Change summary by file extension: .json : +4 -0 ``` > 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.