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

Bump the java-test-dependencies group across 1 directory with 3 updates #62

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 1, 2024

Bumps the java-test-dependencies group with 3 updates in the / directory: org.junit.jupiter:junit-jupiter, org.mockito:mockito-core and org.hamcrest:hamcrest.

Updates org.junit.jupiter:junit-jupiter from 5.10.2 to 5.11.0

Release notes

Sourced from org.junit.jupiter:junit-jupiter's releases.

JUnit 5.11.0 = Platform 1.11.0 + Jupiter 5.11.0 + Vintage 5.11.0

See Release Notes.

New Contributors

Full Changelog: junit-team/junit5@r5.10.3...r5.11.0

JUnit 5.11.0-RC1 = Platform 1.11.0-RC1 + Jupiter 5.11.0-RC1 + Vintage 5.11.0-RC1

See Release Notes.

New Contributors

Full Changelog: junit-team/junit5@r5.11.0-M2...r5.11.0-RC1

JUnit 5.11.0-M2 = Platform 1.11.0-M2 + Jupiter 5.11.0-M2 + Vintage 5.11.0-M2

See Release Notes.

New Contributors

Full Changelog: junit-team/junit5@r5.11.0-M1...r5.11.0-M2

JUnit 5.11.0-M1 = Platform 1.11.0-M1 + Jupiter 5.11.0-M1 + Vintage 5.11.0-M1

... (truncated)

Commits
  • 6b8e42b Release 5.11
  • 9430ece Allow potentially unlimited maxCharsPerColumn in Csv{File}Source (#3924)
  • 0b10f86 Polish release notes
  • 4dbd0f9 Let @TempDir fail fast with File annotated element and non-default file s...
  • 57f1ad4 Fix syntax
  • d78730a Prioritize tasks on critical path of task graph
  • b6719e2 Remove obsolete directory
  • d8ec757 Apply Spotless formatting to Gradle script plugins
  • dae525d Disable caching of some Spotless tasks due to negative avoidance savings
  • c63d118 Re-enable caching verifyOSGi tasks (issue was fixed in bnd 7.0.0)
  • Additional commits viewable in compare view

Updates org.mockito:mockito-core from 5.11.0 to 5.13.0

Release notes

Sourced from org.mockito:mockito-core's releases.

v5.13.0

Changelog generated by Shipkit Changelog Gradle Plugin

5.13.0

v5.12.0

... (truncated)

Commits
  • 9a7e7ea Replace dependencies.gradle with libs.versions.toml
  • 1b7675c Allow links to JUnit Jupiter Javadoc
  • f6450a0 Bump versions.bytebuddy from 1.14.19 to 1.15.0 (#3429)
  • 77c3197 Bump org.jetbrains.kotlin:kotlin-stdlib from 2.0.10 to 2.0.20 (#3427)
  • 0e59624 Bump org.junit.platform:junit-platform-launcher from 1.10.3 to 1.11.0 (#3425)
  • 40925b6 Bump com.gradle.enterprise from 3.17.6 to 3.18 (#3423)
  • 84f605d Fix a typo in InjectMocks (#3422)
  • 87e4a4f Bump versions.bytebuddy from 1.14.18 to 1.14.19 (#3417)
  • 819cc6f Bump androidx.test:runner from 1.6.1 to 1.6.2 (#3415)
  • 90df798 Bump versions.junitJupiter from 5.10.3 to 5.11.0 (#3413)
  • Additional commits viewable in compare view

Updates org.hamcrest:hamcrest from 2.2 to 3.0

Release notes

Sourced from org.hamcrest:hamcrest's releases.

Hamcrest v3.0

Breaking Changes

  • From version 3.0, the jar distributed to Maven Central is now compiled to Java 1.8 bytecode, and is not compatible with previous versions of Java. See [Issue #331](hamcrest/JavaHamcrest#331) and [PR #411](hamcrest/JavaHamcrest#411) for details. Developers who use Java 1.7 earlier can still depend upon hamcrest-2.2.jar.

Improvements

Hamcrest v3.0-rc1

Breaking Changes

  • From version 3.0, the jar distributed to Maven Central is now compiled to Java 1.8 bytecode, and is not compatible with previous versions of Java. See [Issue #331](hamcrest/JavaHamcrest#331) and [PR #411](hamcrest/JavaHamcrest#411) for details. Developers who use Java 1.7 earlier can still depend upon hamcrest-2.2.jar.

Improvements

Changelog

Sourced from org.hamcrest:hamcrest's changelog.

Version 3.0 (1st August 2024)

Breaking Changes

  • From version 3.0, the jar distributed to Maven Central is now compiled to Java 1.8 bytecode, and is not compatible with previous versions of Java. See [Issue #331](hamcrest/JavaHamcrest#331) and [PR #411](hamcrest/JavaHamcrest#411) for details. Developers who use Java 1.7 earlier can still depend upon hamcrest-2.2.jar.

Improvements

Commits
  • 68984b8 Version 3.0
  • 1adc351 Fix javadoc title
  • 4e2b71c Add instructions for releasing to Maven Central
  • 3fa841d Revert version to 3.0-SNAPSHOT
  • 750dc36 Prepare for version 3.0-rc1
  • 1703e95 Fix broken tutorial link in README
  • c4578ef Upgrade Gradle 8.8 -> 8.9
  • a9923af Remove old, unused build definitions
  • cf25e14 Cleanup README, fix broken links
  • bc4769e Upgrade to GitHub-native Dependabot (#342)
  • Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps the java-test-dependencies group with 3 updates in the / directory: [org.junit.jupiter:junit-jupiter](https://github.com/junit-team/junit5), [org.mockito:mockito-core](https://github.com/mockito/mockito) and [org.hamcrest:hamcrest](https://github.com/hamcrest/JavaHamcrest).


Updates `org.junit.jupiter:junit-jupiter` from 5.10.2 to 5.11.0
- [Release notes](https://github.com/junit-team/junit5/releases)
- [Commits](junit-team/junit5@r5.10.2...r5.11.0)

Updates `org.mockito:mockito-core` from 5.11.0 to 5.13.0
- [Release notes](https://github.com/mockito/mockito/releases)
- [Commits](mockito/mockito@v5.11.0...v5.13.0)

Updates `org.hamcrest:hamcrest` from 2.2 to 3.0
- [Release notes](https://github.com/hamcrest/JavaHamcrest/releases)
- [Changelog](https://github.com/hamcrest/JavaHamcrest/blob/master/CHANGES.md)
- [Commits](hamcrest/JavaHamcrest@v2.2...v3.0)

---
updated-dependencies:
- dependency-name: org.junit.jupiter:junit-jupiter
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: java-test-dependencies
- dependency-name: org.mockito:mockito-core
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: java-test-dependencies
- dependency-name: org.hamcrest:hamcrest
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: java-test-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Sep 1, 2024
Copy link

coderabbitai bot commented Sep 1, 2024

Walkthrough

The pom.xml file has been updated to reflect new versions for several testing dependencies. Specifically, JUnit Jupiter, Mockito, and Hamcrest versions have been incremented to 5.11.0, 5.13.0, and 3.0, respectively. These updates maintain the overall structure and functionality of the project while ensuring compatibility with newer library features.

Changes

File Change Summary
pom.xml Updated JUnit Jupiter from 5.10.2 to 5.11.0, Mockito from 5.11.0 to 5.13.0, and Hamcrest from 2.2 to 3.0.

Sequence Diagram(s)

(No sequence diagrams generated as the changes do not warrant a visual representation.)

Poem

🐰 In the garden of code, we hop and play,
With JUnit and Mockito, brightening the day!
Hamcrest now dances, in version three,
Testing is joyful, as happy as can be!
So let’s celebrate with a bounce and a cheer,
For our code is now better, let’s spread the good cheer! 🎉


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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ac19927 and 59eb287.

Files selected for processing (1)
  • pom.xml (1 hunks)
Additional comments not posted (3)
pom.xml (3)

27-27: LGTM! The JUnit Jupiter version update looks good.

Updating the JUnit Jupiter version to 5.11.0 is a standard practice to leverage new features, bug fixes, and improvements. The PR summary provides helpful insights into the notable changes made in this version.


28-28: LGTM! The Mockito version update looks good.

Updating the Mockito version to 5.13.0 is a standard practice to leverage new features, bug fixes, and improvements. The PR summary provides helpful insights into the changes made in this version, such as dependency updates, issue fixes, and documentation improvements.


29-29: Verify Java version compatibility with the updated Hamcrest version.

Updating the Hamcrest version to 3.0 is a standard practice to leverage new features, bug fixes, and improvements. However, please note that this version introduces a breaking change:

The jar is now compiled to Java 1.8 bytecode, making it incompatible with earlier Java versions.

Ensure that the project's Java version is compatible with the updated Hamcrest version to avoid any runtime issues. You can run the following script to verify the Java version used in the project:

Verification successful

Java version is compatible with the updated Hamcrest version.

The project's Java version is set to 11, which is compatible with Hamcrest 3.0 as it requires Java 1.8 or higher. There should be no issues related to Java version compatibility due to this update.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the project's Java version compatibility with Hamcrest 3.0.

# Test: Search for the Java version used in the project. Expect: Java version >= 1.8.
rg --type xml $'<release>' pom.xml

Length of output: 62

@infeo
Copy link
Member

infeo commented Oct 30, 2024

@dependabot squash & merge

@infeo infeo added this to the next milestone Oct 30, 2024
@dependabot dependabot bot merged commit dfdd89b into develop Oct 30, 2024
5 checks passed
@dependabot dependabot bot deleted the dependabot/maven/java-test-dependencies-8eaaa57385 branch October 30, 2024 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file java Pull requests that update Java code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant