Bump version to 2.0.0

[jeremyprime]

Summary

Bump project version to 2.0.0 for upcoming release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 88956287-6870-4187-a7fb-52b457da3b7e

📥 Commits

Reviewing files that changed from the base of the PR and between 4fa1bb0 and 65f407b.

📒 Files selected for processing (22)

• examples/boot-iam-auth/pom.xml
• examples/boot-telemetry/pom.xml
• examples/cache/pom.xml
• examples/cluster-pipeline/pom.xml
• examples/cluster/pom.xml
• examples/collections/pom.xml
• examples/operations/pom.xml
• examples/pipeline/pom.xml
• examples/pom.xml
• examples/quickstart/pom.xml
• examples/repositories/pom.xml
• examples/scripting/pom.xml
• examples/serialization/pom.xml
• examples/spring-boot/pom.xml
• examples/streams/pom.xml
• examples/telemetry/pom.xml
• examples/transactions/pom.xml
• performance/pom.xml
• pom.xml
• spring-boot-starter-data-valkey/pom.xml
• spring-data-valkey/pom.xml
• spring-data-valkey/src/main/resources/notice.txt

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request updates Maven project and parent versions from 1.0.0 to 2.0.0 across the root project, modules, performance project, and examples. The Spring Data Valkey notice also changes from 0.1.0 to 2.0.0.

Changes

Version alignment

Layer / File(s)	Summary
Maven version updates pom.xml, spring-data-valkey/pom.xml, spring-boot-starter-data-valkey/pom.xml, performance/pom.xml, examples/*/pom.xml	The root project and child Maven projects now use version 2.0.0 instead of 1.0.0.
Release notice update spring-data-valkey/src/main/resources/notice.txt	The notice now identifies Spring Data Valkey as version 2.0.0 instead of 0.1.0.

Merge Risk: ⚪ Minimal · up to 65f40

This PR updates the project version consistently across the listed files. No actionable merge-blocking risk remains after the normal build and test checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: updating the project version to 2.0.0.
Description check	✅ Passed	The description is directly related to the changes and explains the version update for the upcoming release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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.}