Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
<parent>
<artifactId>verapdf-parent</artifactId>
<groupId>org.verapdf</groupId>
<version>1.29.1</version>
<version>1.29.6</version>
Copy link

Choose a reason for hiding this comment

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

⚠️ 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.

</parent>

<groupId>org.verapdf</groupId>
Expand Down