Bump the production-dependencies group with 4 updates

[dependabot]

Bumps the production-dependencies group with 4 updates: org.projectlombok:lombok, joda-time:joda-time, com.google.guava:guava and org.apache.maven.plugins:maven-surefire-plugin.

Updates org.projectlombok:lombok from 1.18.36 to 1.18.38

Changelog

Sourced from org.projectlombok:lombok's changelog.

v1.18.38 (March 31st, 2025)

• PLATFORM: JDK24 support added.
• FEATURE: Lombok's nullity annotation now supports JSpecify out of the box, using config key jspecify.
• BUGFIX: Recent eclipse releases would get you 'negative length' error. The bug had always been in lombok but didn't matter until recent releases. [Issue #3823](projectlombok/lombok#3823).
• BUGFIX: The 'extract local variable' refactor script of VSCode wouldn't replace all occurrences if run on a method call to a lombok generated method. [Issue #3783](projectlombok/lombok#3783).

Commits

• 37b7e19 [release] pre-release version bump for v1.18.38
• ec886ae [changelog] Mention fixing of #3783 in changelog.
• ed0965b [docs] Cleaned up use of \<p> in maven and edge html.
• b7896c5 #3824 Our own 'Comment' ad hoc impl now also needs to provide an impl for `...
• 8ed8234 [unused-code] We kept a ref to the storeEnd in PrettyPrinter but we never u...
• 975f96f Merge pull request #3856 from mmoayyed/github-workflow-config
• 7783760 Fix github workflow YAML configuration
• 3aa9779 [changelog] Mention fix for eclipse negative length (#3823) in changelog.
• f4e5bbb [fix #3839] Fixing a mistake in my merge of 3939.
• 41dfb0d [fix #3825] Stub compilation requires all non-core-java classes to be stubbed.
• Additional commits viewable in compare view

Updates joda-time:joda-time from 2.13.1 to 2.14.0

Release notes

Sourced from joda-time:joda-time's releases.

Release v2.14.0

See the change notes for more information.

What's Changed

• Update time zone data to 2025bgtz by @​jodastephen in JodaOrg/joda-time#807
• Update build scripts by @​jodastephen in JodaOrg/joda-time#808
• Fix to run locally by @​jodastephen in JodaOrg/joda-time#809
• Setup release from GitHub by @​jodastephen in JodaOrg/joda-time#810

Full Changelog: JodaOrg/joda-time@v2.13.1...v2.14.0

Commits

• a963c21 Release v2.14.0
• 74d44e2 Setup release from GitHub (#810)
• 9a5d753 Fix to run locally (#809)
• e2387d7 Update build scripts (#808)
• f8ee513 Update time zone data to 2025bgtz (#807)
• 13a8f0c Update TZDB build script
• 15c3df5 Update timezone list and docs
• See full diff in compare view

Updates com.google.guava:guava from 33.4.5-jre to 33.4.6-jre

Release notes

Sourced from com.google.guava:guava's releases.

33.4.6

Guava 33.4.6 fixes two problems that we introduced while modularizing Guava in 33.4.5.

Even if you're not upgrading from Guava 33.4.0 or earlier, still read the release notes for Guava 33.4.1. Those release notes contain information about Guava 33.4.5 and 33.4.6's effect on the module system.

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.4.6-jre</version>
  <!-- or, for Android: -->
  <version>33.4.6-android</version>
</dependency>

Jar files

• 33.4.6-jre.jar
• 33.4.6-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.3.jar

Javadoc

• 33.4.6-jre
• 33.4.6-android

JDiff

• 33.4.6-jre vs. 33.4.5-jre
• 33.4.6-android vs. 33.4.5-android
• 33.4.6-android vs. 33.4.6-jre

Changelog

• Removed the extra copy of each class from the Guava jar. The extra copies were an accidental addition from the modularization work in Guava 33.4.5. (40485b93ce)
• Fixed annotation-related warnings when using Guava in modular builds. The most common such warning is Cannot find annotation method 'value()' in type 'DoNotMock': .... (7e15ab3566)

Commits

• See full diff in compare view

Updates org.apache.maven.plugins:maven-surefire-plugin from 3.5.2 to 3.5.3

Release notes

Sourced from org.apache.maven.plugins:maven-surefire-plugin's releases.

3.5.3

🐛 Bug Fixes

• [SUREFIRE-1737] - Fix disable in statelessTestsetReporter (#816) @​slawekjaranowski
• [SUREFIRE-1643] - surefire junit5 parallel tests (#815) @​olamy
• [SUREFIRE-2289] - Make exceptions more appropriate to context (#798) @​elharo

👻 Maintenance

• surefire shared utils version current version (#825) @​olamy
• Update site descriptors (#821) @​slawekjaranowski
• Use newer version of surefire for itself testing, enable JUnit 5 in tests (#822) @​slawekjaranowski
• Remove dependencies from root pom (#819) @​slawekjaranowski
• move this dependency to dptMngt (#818) @​olamy
• [SUREFIRE-2291] - Change logger from Plexus to SLF4J (#811) @​jeffjensen
• Add GitHub Automation actions (#812) @​slawekjaranowski
• Convert reports to Guice (#803) @​elharo
• [MNGSITE-529] - Rename "Goals" to "Plugin Documentation" (#809) @​Bukama
• Update encoding docs (#802) @​elharo
• Guice injection (#801) @​elharo

📦 Dependency updates

• Bump org.htmlunit:htmlunit from 4.10.0 to 4.11.1 (#823) @dependabot[bot]
• Bump parent to 44 (#817) @​slawekjaranowski
• Bump org.codehaus.plexus:plexus-java from 1.3.0 to 1.4.0 (#810) @dependabot[bot]
• Bump org.htmlunit:htmlunit from 4.4.0 to 4.10.0 (#813) @dependabot[bot]
• Bump commons-io:commons-io from 2.17.0 to 2.18.0 (#797) @dependabot[bot]
• Bump org.assertj:assertj-core from 3.27.2 to 3.27.3 (#807) @dependabot[bot]
• Bump org.assertj:assertj-core from 3.27.0 to 3.27.2 (#805) @dependabot[bot]
• Bump org.assertj:assertj-core from 3.26.3 to 3.27.0 (#800) @dependabot[bot]

Commits

• 4434650 [maven-release-plugin] prepare release surefire-3.5.3
• 1270950 use github directly
• 59f3a1f release tag name backward compatible
• dfbabe2 assertj-core must be test scope (#826)
• e1f8119 back to 3.5.3-SNAPSHOT
• c497559 [maven-release-plugin] prepare for next development iteration
• 3962112 [maven-release-plugin] prepare release v3.5.3
• 227c134 surefire shared utils version current version (#825)
• 1d34c34 Bump org.htmlunit:htmlunit from 4.10.0 to 4.11.1
• 906b65a Update site descriptors
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.