Skip to content

Conversation

@MaximPlusov
Copy link
Contributor

@MaximPlusov MaximPlusov commented Feb 12, 2026

Summary by CodeRabbit

  • Chores
    • Updated the build parent/platform to a newer release.
    • Advanced and narrowed the supported VeraPDF version range.
    • Replaced/verifier-related components used by tooling and examples to align with the new VeraPDF artifacts and version.

@coderabbitai
Copy link

coderabbitai bot commented Feb 12, 2026

📝 Walkthrough

Walkthrough

Updated parent POM to 1.31.1, narrowed verapdf.version range to [1.31.0,1.32.0-RC), and adjusted verapdf-related dependency coordinates in two module POMs (artifactId and groupId changes).

Changes

Cohort / File(s) Summary
Root POM
pom.xml
Bumped parent POM from 1.29.6 to 1.31.1 and updated verapdf.version property range from [1.29.0,1.30.0-RC) to [1.31.0,1.32.0-RC).
Policy generator POM
policy-generator/pom.xml
Changed dependency artifactId: org.verapdf.apps:greenfield-apps:${verapdf.version}org.verapdf.apps:cli:${verapdf.version}.
Examples POM
verapdf-examples/pom.xml
Replaced dependency coordinates: org.verapdf.apps:greenfield-apps:${verapdf.version}org.verapdf:validation-model:${verapdf.version} (groupId and artifactId changed).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

🐇 I hopped through XML, nibbled lines of pom,
Swapped greenfields for cli and validation calm,
A version whisper—now 1.31 clear,
I leave a little carrot and a tiny cheer. 🥕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Update verapdf version' directly describes the main change: updating verapdf dependency versions across multiple pom.xml files from 1.29.x to 1.31.x.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch verapdf_version

No actionable comments were generated in the recent review. 🎉


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

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@policy-generator/pom.xml`:
- Around line 51-55: Replace the invalid dependency org.verapdf.apps:cli with
the artifact that actually provides the CLI classes
(org.verapdf.cli.commands.VeraCliArgParser etc.); revert the dependency to
org.verapdf.apps:greenfield-apps (or the correct verapdf CLI artifact) in the
pom entry currently using org.verapdf.apps:cli and keep the version tied to
${verapdf.version} ensuring that property resolves to a version in the
[1.31.0,1.32.0-RC) range so the required classes are present at build time.

@MaximPlusov MaximPlusov merged commit 2480ef0 into master Feb 12, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant