Skip to content

chore: Configure Renovate #235

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

Closed
wants to merge 1 commit into from
Closed

chore: Configure Renovate #235

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 7, 2025

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

  • .github/workflows/build.yaml (github-actions)
  • .github/workflows/publish.yaml (github-actions)
  • pom.xml (maven)
  • package.json (npm)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 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 16 Pull Requests:

chore(deps): update dependency com.puppycrawl.tools:checkstyle to v10.23.1
chore(deps): update dependency org.apache.maven.plugins:maven-deploy-plugin to v3.1.4
  • Schedule: ["at any time"]
  • Branch name: renovate/maven-deploy-plugin-version
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-deploy-plugin to 3.1.4
chore(deps): update dependency org.jacoco:jacoco-maven-plugin to v0.8.13
chore(deps): update slf4j monorepo to v2.0.17
fix(deps): update dependency com.google.code.gson:gson to v2.13.1
chore(deps): update dependency org.apache.maven.plugins:maven-checkstyle-plugin to v3.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/checkstyle-plugin-version
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-checkstyle-plugin to 3.6.0
chore(deps): update dependency org.apache.maven.plugins:maven-compiler-plugin to v3.14.0
  • Schedule: ["at any time"]
  • Branch name: renovate/compiler-plugin-version
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-compiler-plugin to 3.14.0
chore(deps): update dependency org.apache.maven.plugins:maven-enforcer-plugin to v3.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/maven-enforcer-version
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-enforcer-plugin to 3.5.0
chore(deps): update dependency org.apache.maven.plugins:maven-gpg-plugin to v3.2.7
  • Schedule: ["at any time"]
  • Branch name: renovate/maven-gpg-plugin-version
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-gpg-plugin to 3.2.7
chore(deps): update dependency org.apache.maven.plugins:maven-javadoc-plugin to v3.11.2
  • Schedule: ["at any time"]
  • Branch name: renovate/org.apache.maven.plugins-maven-javadoc-plugin-3.x
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-javadoc-plugin to 3.11.2
chore(deps): update dependency org.apache.maven.plugins:maven-source-plugin to v3.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/org.apache.maven.plugins-maven-source-plugin-3.x
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-source-plugin to 3.3.1
chore(deps): update dependency org.apache.maven.plugins:maven-surefire-plugin to v3.5.3
  • Schedule: ["at any time"]
  • Branch name: renovate/surefire-version
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-surefire-plugin to 3.5.3
chore(deps): update dependency org.sonatype.plugins:nexus-staging-maven-plugin to v1.7.0
chore(deps): update dependency semantic-release to v21.1.2
  • Schedule: ["at any time"]
  • Branch name: renovate/semantic-release-monorepo
  • Merge into: main
  • Upgrade semantic-release to 21.1.2
chore(deps): update semantic-release monorepo (major)
fix(deps): update kotlin monorepo to v2 (major)

🚸 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.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@pyrooka
Copy link
Member

pyrooka commented May 14, 2025

Closing this as in an internal discussion we've decided to keep managing the dependencies by hand.

@pyrooka pyrooka closed this May 14, 2025
@pyrooka pyrooka deleted the renovate/configure branch May 14, 2025 17:40
Copy link
Author

renovate bot commented May 14, 2025

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants