Update Selenium to 4.40.0 +semver:feature

[mialeska]

Update license year

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]

Walkthrough

Updated copyright year from 2025 to 2026 in the LICENSE file. Updated Maven dependencies in pom.xml: jackson-databind from 2.19.2 to 2.20.1 and selenium-java from 4.39.0 to 4.40.0.

Changes

Cohort / File(s)	Summary
Copyright Year Update LICENSE	Copyright year bumped from 2025 to 2026 in Apache 2.0 license header
Dependency Version Bumps pom.xml	jackson-databind: 2.19.2 → 2.20.1; selenium-java: 4.39.0 → 4.40.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update Selenium to 4.25.0 #97: Both PRs update jackson-databind and selenium-java dependencies to newer versions in pom.xml.
• Update Selenium to 4.28.1 +semver:feature #100: Both PRs update the copyright year in LICENSE and bump the selenium-java dependency version.
• Update Selenium to 4.28.1 +semver:feature #99: Both PRs modify the LICENSE copyright year and update the selenium-java dependency in pom.xml.

Poem

🐰 A year hops forward, twenty-twenty-six,
Dependencies dance to their newest mixes,
Jackson grins and Selenium shines,
Maintenance done in record time,
Hop hooray for version lines! ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title focuses on Selenium update to 4.40.0, but the PR description emphasizes license year update as primary change, creating misalignment with actual main change.	Revise title to reflect the primary change (license year update) or clarify that Selenium update is the main focus if that was the intent.
Description check	⚠️ Warning	Description includes title-level summary and partially completes checklist, but lacks critical required sections: no related issue link, no testing details, and incomplete checklist items.	Add related issue link, describe testing methodology and environment, and complete all required checklist items with explanations.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-selenium-to-4.40.0

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@pom.xml`:
- Around line 119-123: The pom declares org.seleniumhq.selenium:selenium-java
with version 4.40.0 which isn't a released artifact and will break the build;
update the <version> for the dependency org.seleniumhq.selenium:selenium-java to
the latest stable (4.39.0) or, if you intentionally need a nightly, replace
4.40.0 with the exact nightly/snapshot coordinate (e.g., 4.40.0-nightly or
4.40.0-SNAPSHOT) and add the appropriate snapshot/nightly repository entry;
ensure you only modify the <version> element inside the selenium-java
<dependency>.