Update parent version to 1.29.6

[LonelyMidoriya]

Summary by CodeRabbit

• Chores
  • Updated build infrastructure dependencies to maintain compatibility and receive latest improvements.

[coderabbitai]

Walkthrough

Updated the Maven parent dependency version from 1.29.1 to 1.29.6 in the project's pom.xml file, representing a patch-level version increment to the parent build configuration.

Changes

Cohort / File(s)	Summary
Maven Parent Version Update pom.xml	Parent version bumped from 1.29.1 to 1.29.6

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single-line version update with no logic or structural changes
• No impact on method signatures or public APIs

Poem

🐰 A version hops along the way,
From one-two-nine-one to point-six today!
The parent builds strong, patch by patch,
Dependencies tidy—a perfect match!
hoppy code compilation ✨

Pre-merge checks and finishing touches

✅ 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 directly and clearly describes the main change: updating the Maven parent version from 1.29.1 to 1.29.6 in pom.xml. It is concise, specific, and accurately represents the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch parent-pom

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aa4d943 and afd6f38.

📒 Files selected for processing (1)

• pom.xml (1 hunks)

⏰ 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). (5)

• GitHub Check: Checkout and Build (8)
• GitHub Check: Checkout and Build (25)
• GitHub Check: Checkout and Build (17)
• GitHub Check: Checkout and Build (11)
• GitHub Check: Checkout and Build (21)

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify parent version 1.29.6 exists and is compatible.

The patch-level version bump from 1.29.1 to 1.29.6 is within the version constraint range specified in the verapdf.version property (lines 40: [1.29.0,1.30.0-RC)). However, ensure that:

1. The verapdf-parent version 1.29.6 is a stable, published release.
2. There are no breaking changes between 1.29.1 and 1.29.6 that would affect child modules or build behavior.
3. All child modules are compatible with the new parent configuration.

---

🏁 Script executed:

#!/bin/bash
# Description: Verify verapdf-parent version 1.29.6 and check for potential breaking changes

# Search for the parent version in the Artifactory repository
# Check if version 1.29.6 is available
curl -s "https://artifactory.openpreservation.org/artifactory/api/storage/vera-dev/org/verapdf/verapdf-parent/1.29.6" \
  | grep -q "org.verapdf" && echo "✓ Version 1.29.6 found in repository" || echo "✗ Version 1.29.6 not found"

# Search for any Maven central or release notes mentioning changes
rg -i "1\.29\.[1-6]|breaking|deprecat" --type xml --type md --type txt pom.xml README.md 2>/dev/null || true

Length of output: 133

---

🌐 Web query:

verapdf-parent version 1.29.6 release notes breaking changes

💡 Result:

I couldn’t find any release or release notes for verapdf-parent version 1.29.6. The veraPDF project releases and Maven artifacts available publicly show current published versions around v1.28 / v1.28.2 (no 1.29.6), and the org.verapdf Maven namespace (including verapdf-parent) is listed on Maven Central. See the project release listings and Maven index for reference. [1][2]

If you want, I can:

• search again (include other registries or a specific GitHub repo/org) or
• check a specific URL/artifact you have that references 1.29.6.

Sources:

1. org.verapdf Maven index (Maven Central listing). [repo1.maven.org]. [turn2search1]
2. veraPDF releases / changelogs (GitHub / Zenodo release records showing v1.28.1 / v1.28.2). [turn1search7][turn2search8]

---

🌐 Web query:

verapdf-parent Maven Central latest version 1.28

💡 Result:

The verapdf 1.28 release series has newer patch releases — the latest published on Maven Central is 1.28.2 (released July 15, 2025). [1][2]

Sources:

• veraPDF GitHub release v1.28.2 (Jul 15, 2025). [1]
• Maven Central / Maven Repository listings for org.verapdf artifacts (1.28.2). [2]

---

Revert parent version to 1.28.2 (latest stable release).

Version 1.29.6 is a development version in the private vera-dev repository and is not a publicly released stable version. The latest published version on Maven Central is 1.28.2 (released July 15, 2025). Using an unreleased development version as a parent dependency will cause build and dependency resolution failures for users without access to the private repository.

Change line 10 from <version>1.29.6</version> to <version>1.28.2</version>.

🤖 Prompt for AI Agents

In pom.xml around line 10, the parent version is set to an internal development
release 1.29.6 which is not published to Maven Central; change the parent
<version> element value from 1.29.6 to the stable published version 1.28.2 so
builds resolve for users without access to the private vera-dev repo.