chore: bump version to 0.1.2-SNAPSHOT

[WilliamAGH]

Bump project version from 0.1.0 to 0.1.2-SNAPSHOT to prepare for the next development cycle.

Version updates

• Update VERSION_NAME in gradle.properties from 0.1.0 to 0.1.2-SNAPSHOT
• Update fallback version in build.gradle.kts from 0.1.0 to 0.1.2

Documentation updates

• Update Gradle dependency example in README.md to 0.1.2
• Update Maven dependency example in README.md to 0.1.2

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated version to 0.1.2 across project configuration and documentation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

Version bump from 0.1.0 to 0.1.2 across project configuration and documentation. README.md, build.gradle.kts, and gradle.properties all updated to reflect the new version, with gradle.properties designating a SNAPSHOT pre-release.

Changes

Cohort / File(s)	Summary
Documentation README.md	Version references updated from 0.1.0 to 0.1.2 in installation notes, Gradle dependency example, and Maven dependency specification
Build Configuration build.gradle.kts, gradle.properties	Version definitions bumped: build.gradle.kts default version changed to 0.1.2; gradle.properties VERSION_NAME updated to 0.1.2-SNAPSHOT

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🚀 From zero-point-one, we take a leap,
Two notches higher, version creep,
A snapshot tagged, pre-release sweet,
Building up to something neat!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The PR description accurately describes the version update changes across README.md, build.gradle.kts, and gradle.properties, directly matching the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title Check	✅ Passed	Title check skipped as CodeRabbit has written the PR title.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dev

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0c6bbc7 and 1da8cf5.

📒 Files selected for processing (3)

• README.md
• build.gradle.kts
• gradle.properties

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Agent

🔇 Additional comments (5)

build.gradle.kts (1)

46-48: LGTM! Version fallback updated correctly. 🎉

The fallback version chain (version → VERSION_NAME → hardcoded default) is a nice pattern! This ensures builds have a sensible version even when properties aren't explicitly configured. The update to 0.1.2 aligns nicely with the README documentation for consumers.

Fun tidbit: This three-tier fallback approach is a great defensive programming practice—it ensures your artifact always has a meaningful version identifier.

gradle.properties (1)

3-3: LGTM! SNAPSHOT version set appropriately for development. ✨

Using the -SNAPSHOT suffix is the classic Maven/Gradle convention for "this is a work-in-progress version." When you're ready to cut the official 0.1.2 release, you'd remove the -SNAPSHOT suffix here.

Quick learning moment: SNAPSHOT artifacts are treated as mutable by Maven repositories—they can be overwritten with newer builds of the same version. Release versions (without SNAPSHOT) are immutable once published!

README.md (3)

13-13: Nice touch with the version reminder! 📚

The "Replace 0.1.2 with the latest release" note is helpful—it gently reminds users that documentation examples may lag behind the actual latest version. Clear and considerate!

---

19-23: Gradle example updated correctly. ✅

The Groovy DSL syntax is spot-on, and the version aligns with the project's release version.

---

27-33: Maven example updated correctly. ✅

The XML snippet follows standard Maven conventions with proper groupId, artifactId, and version elements. Users can copy-paste this directly into their pom.xml.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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

[Copilot]

Pull request overview

This PR updates the project version from 0.1.0 to 0.1.2 across configuration and documentation files to reflect a new release version.

Changes:

• Updated VERSION_NAME in gradle.properties to 0.1.2-SNAPSHOT
• Updated fallback version in build.gradle.kts to 0.1.2
• Updated documentation examples in README.md to reference version 0.1.2

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
gradle.properties	Updated VERSION_NAME to 0.1.2-SNAPSHOT
build.gradle.kts	Updated fallback version from 0.1.0 to 0.1.2
README.md	Updated installation examples and instructions to reference version 0.1.2

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The VERSION_NAME is set to 0.1.2-SNAPSHOT, which indicates a development/pre-release version, but the PR description and README.md indicate this is meant to be a production release version 0.1.2. For a release, the VERSION_NAME should be 0.1.2 without the -SNAPSHOT suffix. The -SNAPSHOT suffix is conventionally used for development versions that are not yet released. If this is intended to be a release, change to VERSION_NAME=0.1.2. If this is preparing for development after the 0.1.2 release, it would typically be 0.1.3-SNAPSHOT instead.

Suggested change

	VERSION_NAME=0.1.2-SNAPSHOT
	VERSION_NAME=0.1.2

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1da8cf5bae

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align VERSION_NAME with published release version

When building or publishing without explicitly passing -Pversion, build.gradle.kts uses VERSION_NAME from gradle.properties, which is now 0.1.2-SNAPSHOT. That means the produced artifact version will be a snapshot even though the README and fallback version were bumped to 0.1.2, so consumers following the README will look for a non‑snapshot release that won't exist (or you’ll publish the wrong coordinate). If this change is meant to update to the 0.1.2 release, VERSION_NAME should match the release version (or the README should stay at snapshot).

Useful? React with 👍 / 👎.