chore(deps): update all non-major dependencies #86
Conversation
![renovate-self-hosted-apter[bot]](https://avatars.githubusercontent.com/u/82641433?s=60&v=4){kind=small}
renovate-self-hosted-apter
bot
added
dependencies
github_actions
gradle
gradle_wrapper
labels
WalkthroughThe changes involve updates to the configuration of GitHub Actions workflows and dependency management in a Gradle project. This includes upgrading specific action versions in the workflow, modifying dependency versions in the Changes
Possibly related issues
Poem
Tip Early access features: enabledWe are currently testing the following features in early access: Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (3)
- .github/workflows/build.yml (3 hunks)
- gradle/libs.versions.toml (1 hunks)
- gradle/wrapper/gradle-wrapper.properties (1 hunks)
Files skipped from review due to trivial changes (1)
- .github/workflows/build.yml
Additional comments not posted (2)
gradle/wrapper/gradle-wrapper.properties (1)
3-3: LGTM! Gradle version updated as expected.The Gradle version has been successfully updated from 8.9 to 8.10, which aligns with the PR objectives.
To ensure smooth integration, please verify that all Gradle-related CI/CD pipelines are compatible with Gradle 8.10. Run the following script to check for any Gradle version references in CI configuration files:
Verification successful
No explicit Gradle version references found in CI/CD configuration files. The search did not reveal any specific references to Gradle versions 8.9 or 8.10 in
.yamlor.ymlfiles, indicating that there are no explicit dependencies on these versions in the CI/CD configurations. This suggests compatibility with the updated Gradle version.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for Gradle version references in CI configuration files # Test: Search for Gradle version references in CI configuration files rg --type yaml '(gradle|version).*8\.(9|10)' .github/Length of output: 55
Script:
#!/bin/bash # Description: Check for Gradle version references in CI/CD configuration files across the repository # Test: Search for Gradle version references in various CI/CD configuration files rg --type yaml --type yml '(gradle|version).*8\.(9|10)' .Length of output: 87
Script:
#!/bin/bash # Description: Check for Gradle version references in CI/CD configuration files across the repository # Test: Search for Gradle version references in files with .yaml and .yml extensions rg '(gradle|version).*8\.(9|10)' --glob '*.yaml' --glob '*.yml' .Length of output: 67
gradle/libs.versions.toml (1)
3-3: LGTM! Dependency versions updated as expected.The following dependency versions have been successfully updated:
- androidToolsCommon: 31.5.1 → 31.6.0
- androidGradle: 8.5.1 → 8.6.0
- gradlePluginPublish: 1.2.1 → 1.2.2
- guava: 33.2.1-jre → 33.3.0-jre
- junit5: 5.10.3 → 5.11.0
These updates align with the PR objectives.
To ensure smooth integration of these updates, please verify the project's build and runtime behavior. Run the following script to check for any potential conflicts or issues:
Also applies to: 6-6, 12-13, 15-15
Verification successful
Dependency Updates Verified Successfully
The dependency versions have been updated as expected in the
gradle/libs.versions.tomlfile. No TODO or FIXME comments related to these updates were found, indicating a smooth integration.
- androidToolsCommon: 31.5.1 → 31.6.0
- androidGradle: 8.5.1 → 8.6.0
- gradlePluginPublish: 1.2.1 → 1.2.2
- guava: 33.2.1-jre → 33.3.0-jre
- junit5: 5.10.3 → 5.11.0
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify project build and look for potential conflicts # Test: Run Gradle build and check for errors ./gradlew build --info # Test: Check for any TODO or FIXME comments related to version updates rg --type-not binary "TODO|FIXME" -C 3 | rg -i "version|update|upgrade|compatibility"Length of output: 328
Script:
#!/bin/bash # Verify the dependency version updates in gradle/libs.versions.toml # Check for the specific version updates in the file rg 'androidToolsCommon\s*=\s*"31\.6\.0"' gradle/libs.versions.toml -A 3 rg 'androidGradle\s*=\s*"8\.6\.0"' gradle/libs.versions.toml -A 3 rg 'gradlePluginPublish\s*=\s*"1\.2\.2"' gradle/libs.versions.toml -A 3 rg 'guava\s*=\s*"33\.3\.0-jre"' gradle/libs.versions.toml -A 3 rg 'junit5\s*=\s*"5\.11\.0"' gradle/libs.versions.toml -A 3 # Check for any TODO or FIXME comments related to version updates rg "TODO|FIXME" -C 3 | rg -i "version|update|upgrade|compatibility"Length of output: 869
Branch Coverage (ubuntu-22.04)
|
Line Coverage (ubuntu-22.04)
|
Branch Coverage (windows-2022)
|
Line Coverage (windows-2022)
|
This PR contains the following updates:
v4.2.1->v4.2.2v4.3.4->v4.4.08.9->8.105.10.3->5.11.033.2.1-jre->33.3.0-jre1.2.1->1.2.28.5.1->8.6.08.5.1->8.6.031.5.1->31.6.0Release Notes
actions/setup-java (actions/setup-java)
v4.2.2Compare Source
What's Changed
Bug fixes:
Documentation changes
Dependency updates:
Full Changelog: actions/setup-java@v4...v4.2.2
actions/upload-artifact (actions/upload-artifact)
v4.4.0Compare Source
Notice: Breaking Changes⚠️
We will no longer include hidden files and folders by default in the
upload-artifactaction of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option,include-hidden-files, to continue to do so.See "Notice of upcoming deprecations and breaking changes in GitHub Actions runners" changelog and this issue for more details.
What's Changed
Full Changelog: actions/upload-artifact@v4.3.6...v4.4.0
v4.3.6Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4...v4.3.6
v4.3.5Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.3.4...v4.3.5
gradle/gradle (gradle)
v8.10: 8.10Compare Source
The Gradle team is excited to announce Gradle 8.10.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Björn Kautler,
Craig Andrews,
gotovsky,
Jeff,
Kirill Gavrilov,
Madalin Valceleanu,
Sergei Vorobev,
Thach Le,
Thad Guidry
Upgrade instructions
Switch your build to use Gradle 8.10 by updating your wrapper:
See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.
For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.