Skip to content

Update CDXA refresh and support additional version numbers - #2210

Merged
johnoliver merged 19 commits into
productionfrom
prod-release-notes
Oct 30, 2026
Merged

johnoliver merged 19 commits into
productionfrom
prod-release-notes

Conversation

@johnoliver

Copy link
Copy Markdown
Contributor

This pull request introduces several improvements and fixes across the codebase, primarily focusing on enhancing version data handling, improving release notes persistence, and updating CI/CD workflows. The most significant changes include hiding internal version number details from the public API, making release notes persistence more robust, and extending workflow triggers to support a new release notes branch.

Version Data Handling and API Visibility:

  • Added an additional_version_numbers property to VersionData for downstream version elements (per JEP 322), and ensured it is hidden from the public API using @JsonbTransient, @JsonIgnore, and OpenAPI schema annotations. Also added a computed version_numbers property, which is similarly hidden. [1] [2] [3]
  • Updated sorting logic in Releases to use a comparator for additional_version_numbers, ensuring correct version ordering.
  • Adjusted VersionRangeFilter to ignore additional_version_numbers in semver mode, preventing mismatches when filtering versions. [1] [2]
  • Enhanced tests in VersionPathTest and VersionRangeFilterTest to verify that additional_version_numbers and version_numbers are hidden from the API and OpenAPI docs, and that semver filtering behaves as expected. [1] [2] [3]

Release Notes Persistence Improvements:

  • Modified the ReleaseNote and ReleaseNotes models to use Jackson annotations for robust deserialization, added a new backportedBy field, and implemented equals/hashCode for correctness.
  • Updated MongoDB persistence logic to create a unique index on the id field for release notes and switched to using replaceOne(..., upsert=true) for atomic updates, improving reliability and preventing duplicates. [1] [2] [3]

CI/CD Workflow Updates:

  • Updated GitHub Actions workflows (ci.yml, deploy-adoptium.yml, deploy-adoptopenjdk.yml) to trigger on the new prod-release-notes branch, in addition to main and production, supporting improved release management. [1] [2] [3]

Dependency Management:

  • Added a dependency on jakarta.json.bind-api to the models module to support new JSON-B annotations.

Checklist

  • You added tests to cover the change
  • mvn clean install build and test completes
  • You changed or added to the documentation

andrew-m-leonard and others added 19 commits October 29, 2026 14:16
…e stale cache

Co-authored-by: Bob <bob@ibm.com>
…pper. Exclude additional numbers from semver pending descision on how to represent it
Support additional version number formats
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
prod-release-notes: fix(release-notes): refresh notes on incremental updates and parse backportedBy
Hide version_numbers from public api
Temporarily hide additional_version_numbers from public endpoint to keep schema stable for now

@andrew-m-leonard andrew-m-leonard left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

looks good

@johnoliver
johnoliver merged commit 5de49be into production Oct 30, 2026
10 of 12 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.

2 participants