release: 1.23.0

[forkline-bot]

Release 1.23.0

Fixed

• Corrected requireNotNull ordering in VersioningPlugin so null checks work as intended

---

This PR was generated by Forkline — AI-powered code contributions.
The agent analyzed the issue and implemented this fix autonomously.

[forkline-bot]

Maintainability Review

Initial expected implementation: matched
Initial reason: PR description states "Corrected requireNotNull ordering in VersioningPlugin so null checks work as intended" — the fix commit (df28be4e) correctly moves .toInt() outside requireNotNull so the null check on getProperty() is reachable.
Applied maintenance work: none
Final implementation: matches
Validation: build-logic:compileKotlin passes

Findings

Priority: low
Category: bug
Decision: do not pursue
Location: VersioningPlugin.kt:46 — .toInt() after requireNotNull
Problem: If the property exists but contains a non-integer value, .toInt() throws NumberFormatException without a helpful message. However, the property file is auto-generated by VersioningTask, so this is extremely unlikely in practice.
Why not worth it: Auto-generated input makes this a theoretical risk; adding toIntOrNull + another requireNotNull adds complexity for negligible payoff.
Risk/scope: trivial change but no meaningful reliability gain