Repository navigation
Update CDXA refresh and support additional version numbers - #2210
Merged
Merged
Conversation
Co-authored-by: Bob <bob@ibm.com>
Co-authored-by: Bob <bob@ibm.com>
…e stale cache Co-authored-by: Bob <bob@ibm.com>
Co-authored-by: Bob <bob@ibm.com>
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
…eep schema stable for now
Temporarily hide additional_version_numbers from public endpoint to keep schema stable for now
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
additional_version_numbersproperty toVersionDatafor 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 computedversion_numbersproperty, which is similarly hidden. [1] [2] [3]Releasesto use a comparator foradditional_version_numbers, ensuring correct version ordering.VersionRangeFilterto ignoreadditional_version_numbersin semver mode, preventing mismatches when filtering versions. [1] [2]VersionPathTestandVersionRangeFilterTestto verify thatadditional_version_numbersandversion_numbersare hidden from the API and OpenAPI docs, and that semver filtering behaves as expected. [1] [2] [3]Release Notes Persistence Improvements:
ReleaseNoteandReleaseNotesmodels to use Jackson annotations for robust deserialization, added a newbackportedByfield, and implementedequals/hashCodefor correctness.idfield for release notes and switched to usingreplaceOne(..., upsert=true)for atomic updates, improving reliability and preventing duplicates. [1] [2] [3]CI/CD Workflow Updates:
ci.yml,deploy-adoptium.yml,deploy-adoptopenjdk.yml) to trigger on the newprod-release-notesbranch, in addition tomainandproduction, supporting improved release management. [1] [2] [3]Dependency Management:
jakarta.json.bind-apito the models module to support new JSON-B annotations.Checklist
mvn clean installbuild and test completes