Update Selenium to 4.28.1 +semver:feature

[mialeska]

PR Details

Related Issue Link:

How Has This Been Tested

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates the LICENSE file by changing the copyright year from 2024 to 2025. In the pom.xml file, several dependency versions are updated (log4j, testng, guava, selenium-java, java-client), and the Maven Assembly Plugin goal is modified from "attached" to "single". These changes focus on maintaining current versioning and adjusting the build configuration.

Changes

File	Change Summary
LICENSE	Updated copyright year from "2024 Aquality Automation" to "2025 Aquality Automation".
pom.xml	Updated dependencies: log4j (2.24.2 → 2.24.3), testng (7.10.2 → 7.11.0), guava (33.3.1-jre → 33.4.0-jre), selenium-java (4.27.0 → 4.28.1), java-client (9.3.0 → 9.4.0); modified Maven Assembly Plugin goal from "attached" to "single".

Possibly related PRs

• Update selenium to 4.22.0 #94: Involved dependency version updates including the selenium-java adjustment, aligning with the current changes.
• Update Selenium to 4.28.1 +semver:feature #99: Addressed similar updates in the LICENSE file and pom.xml modifications.
• Update Selenium to 4.25.0 #97: Focused on updating the selenium-java dependency, reflecting a direct connection with these modifications.

Suggested labels

java, dependencies

Poem

I'm a jittery bunny, quick on my feet,
Hopping through code where changes meet.
The LICENSE now wears a 2025 glow,
Dependencies leap to versions new as they go.
With a twitch and a hop, this rabbit sings—
Cheers to updates and the joy that they bring!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2bad0e4 and 45b0e20.

📒 Files selected for processing (2)

• LICENSE (1 hunks)
• pom.xml (5 hunks)

---

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

• 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. (Beta)
• @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.