chore(master): release 0.12.0

[boolivar]

🤖 I have created a release beep boop

0.12.0 (2026-04-12)

Features

• java21 (#121) (d20a446)
• jspecify (#122) (1cc18bc)
• spockframework v2.4 (#119) (c0d8207)

---

This PR was generated with Release Please. See documentation.

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Fix invalid comment in code example Replace the invalid HTML comment in the Gradle code example with a valid Groovy comment (//) to ensure the code snippet is usable. README.md [251-260] <pre> repositories { mavenCentral() } dependencies { - <!-- x-release-please-version -->testRuntimeOnly "io.github.boolivar.jdoctest:jdoc-cucumber:0.12.0" + // x-release-please-version + testRuntimeOnly "io.github.boolivar.jdoctest:jdoc-cucumber:0.12.0" testImplementation "io.cucumber:cucumber-java:7.17.0" } </pre> [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies an invalid HTML comment within a Gradle code example, which would cause a build failure for users who copy the snippet, thus improving the documentation's accuracy.	Low
Update

[boolivar]

🤖 Created releases:

• 0.12.0

🌻