chore: bump to 1.2.2

[imnotjames]

Bump the version so we update the package. This should have been done with 1.2.1 but it was missed.

Summary by CodeRabbit

• Chores
  • Updated the application version to 1.2.2.

[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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8f981f83-0a7d-430c-9015-55129331390d

📥 Commits

Reviewing files that changed from the base of the PR and between 80039b8 and 1e73fa5.

📒 Files selected for processing (1)

• build.gradle.kts

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• grimmory-tools/grimmory-docs (manual)

📜 Recent review details

⏰ Context from checks skipped due to timeout. (9)

• GitHub Check: Build on windows-2025 (windows-x64)
• GitHub Check: Build on ubuntu-24.04-arm (linux-arm64)
• GitHub Check: Verify Musl Hardening (arm64)
• GitHub Check: Build on macos-15-intel (darwin-x64)
• GitHub Check: Build on macos-15 (darwin-arm64)
• GitHub Check: Build on ubuntu-24.04 (linux-x64)
• GitHub Check: Verify Musl Hardening (x64)
• GitHub Check: Analyze (c-cpp)
• GitHub Check: Analyze (java-kotlin)

🔇 Additional comments (1)

build.gradle.kts (1)

18-18: LGTM!

---

📝 Walkthrough

Walkthrough

The Gradle project version was bumped from 1.2.0 to 1.2.2 in the allprojects configuration.

Changes

Project version update

Layer / File(s)	Summary
Update project version build.gradle.kts	The allprojects version property changes from 1.2.0 to 1.2.2.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested labels: chore

Suggested reviewers: balazs-szucs

Poem

I’m a bunny with a version to cheer,
1.2.2 is hopping here!
One tiny bump, the build files sing,
Fresh new numbers take wing.
Hop, hop—release bells ring!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title uses conventional commit format and accurately summarizes the version bump.
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.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch imnotjames-patch-1

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch imnotjames-patch-1

---

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

[qodo-code-review]

PR Summary by Qodo

Bump project version to 1.2.2

⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Update Gradle project version to 1.2.2.
• Ensure package publishing reflects the intended release version.

High-Level Assessment

The following are alternative approaches to this PR:

1. Automate versioning via release plugin (e.g., semantic-release / Gradle release)

• ➕ Prevents missed version bumps by making releases deterministic
• ➕ Can generate changelogs and tags consistently
• ➖ Adds CI/release workflow complexity
• ➖ May require adopting/aligning a versioning convention (e.g., Conventional Commits)

2. Derive version from Git tags at build time

• ➕ Eliminates manual version edits in build files
• ➕ Keeps build artifacts traceable to source tags
• ➖ Requires tagging discipline and build environment Git metadata
• ➖ Can complicate local builds without tags

Recommendation: For now, this manual bump is appropriate and low-risk. If missed version updates are recurring, adopt a lightweight release/version automation approach to prevent manual drift and ensure publishing always matches intended releases.

Files changed (1) +1 / -1

Other (1) +1 / -1

build.gradle.ktsSet Gradle project version to 1.2.2 +1/-1

Set Gradle project version to 1.2.2

• Updates the root project version from 1.2.0 to 1.2.2 so published artifacts use the intended release version.

build.gradle.kts

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 1 rule

1. README version mismatch ✗ Dismissed 🐞 Bug ⚙ Maintainability

Description

After bumping the published artifact version to 1.2.2, README installation snippets still hardcode
1.2.0, which will direct users to depend on an outdated release. This is especially confusing for
consumers who copy/paste the Gradle/Maven examples verbatim.

Code

build.gradle.kts[18]

+    version = "1.2.2"

Relevance

⭐⭐⭐ High

PR #79 updated README dependency versions with releases; indicates team keeps install snippets in
sync with published version.

PR-#79
PR-#11

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

build.gradle.kts sets the project version to 1.2.2, but the README’s Gradle and Maven dependency
examples still instruct users to use 1.2.0, making the docs inconsistent with the version being
published after this PR.

build.gradle.kts[16-19]
README.md[83-110]
README.md[115-135]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The project version is now `1.2.2`, but `README.md` still shows dependency coordinates using `1.2.0`. This creates immediate documentation drift and can cause users to install an old version.

### Issue Context
Gradle publishes with `project.version`, so the released artifacts will be `1.2.2`.

### Fix Focus Areas
- README.md[83-110]
- README.md[115-135]

### Suggested change
Replace all occurrences of `org.grimmory:pdfium4j:1.2.0` (and the Maven `<version>1.2.0</version>` entries) with `1.2.2`, or switch the README to a single placeholder like `<latest>` / `x.y.z` to avoid future drift.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---