Bump version for release

[lealobanov]

Description

Bump version for release

---

For contributor use:

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the standards mentioned here.
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

Summary by CodeRabbit

• Chores
  • Updated the default version from "2.0.1" to "2.1.1" for improved dependency management.

[coderabbitai]

Walkthrough

The changes in this pull request involve an update to the build.gradle.kts file, specifically changing the defaultVersion variable from "2.0.1" to "2.1.1". This modification affects how the project version is referenced in the build configuration but does not alter the logic within the subprojects block or the Kotlin compiler options. The overall structure and functionality of the build script remain unchanged.

Changes

File	Change Summary
build.gradle.kts	Updated defaultVersion from "2.0.1" to "2.1.1".

Possibly related PRs

• Bump version #78: This PR also updates the defaultVersion variable in build.gradle.kts, indicating a version bump that could relate to dependency management.
• (WIP) Bump bouncycastle to address vulnerabilities #103: This PR modifies the defaultVersion variable in build.gradle.kts, changing it from "2.0.0" to "2.0.1", which is similar in nature to the version update in the main PR.

Suggested reviewers

• franklywatson

Poem

🐇 In the meadow, hop and play,
A version change has come our way!
From "two-oh-one" to "two-one-one,"
The build is bright, let’s have some fun!
With every hop, our code will sing,
A joyful tune for this new spring! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4b6ff14 and fc1a2df.

📒 Files selected for processing (1)

• build.gradle.kts (1 hunks)

🔇 Additional comments (3)

build.gradle.kts (3)

Line range hint 44-49: Verify version propagation to all subprojects

The version change will propagate to all subprojects. Please ensure this is intended for all modules.

Let's verify the impact:

✅ Verification successful

Version configuration is properly propagated and safe to modify

The version configuration is correctly set up:

• Root build.gradle.kts defines the version logic that propagates to subprojects
• No subprojects override this version explicitly
• The only version references found are for plugin versions and dependencies
• The version is properly used in maven publish coordinates

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any hardcoded versions in subproject build files
fd -e gradle -e kts | xargs rg -l "2\.0\.1"

# Check for version-dependent configurations
fd -e gradle -e kts | xargs rg -l "version"

Length of output: 198

---

Script:

#!/bin/bash
# Check the version usage context in each file
echo "=== settings.gradle.kts ==="
rg "version" settings.gradle.kts -C 2

echo -e "\n=== sdk/build.gradle.kts ==="
rg "version|2\.0\.1" sdk/build.gradle.kts -C 2

echo -e "\n=== java-example/build.gradle.kts ==="
rg "version" java-example/build.gradle.kts -C 2

echo -e "\n=== build.gradle.kts ==="
rg "version" build.gradle.kts -C 2

Length of output: 1775

---

6-6: Verify version bump compliance with semver

The version is being bumped from 2.0.1 to 2.1.1, skipping 2.1.0. While this is technically valid semver, please ensure this is intentional and properly documented in the changelog.

Let's verify the changelog and release documentation:

---

6-6: Verify release process compliance

As this is a version bump for release:

1. Ensure this change is part of a planned release cycle
2. Verify that all release prerequisites are met
3. Check if release notes are prepared

Let's verify the release documentation:

---

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

[github-actions]

Unit Test Results

  62 files  ±0    62 suites  ±0   25s ⏱️ ±0s
397 tests ±0  397 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit f51754a. ± Comparison against base commit f51754a.

[github-actions]

Integration Test Results

  6 files  ±0    6 suites  ±0   3m 30s ⏱️ ±0s
41 tests ±0  40 ✔️ ±0  0 💤 ±0  1 ❌ ±0 

For more details on these failures, see this check.

Results for commit f51754a. ± Comparison against base commit f51754a.