Release 6.5.3: Gradle JDK 21 fix + OpenAPI 3.1 refinements (enum metadata, deprecated)#384
Merged
jemacineiras merged 3 commits intoJul 24, 2026
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
The gradle-portal-push workflow set up JDK 17 and then ran `mvn install` on multiapi-engine, which compiles with `release 21` — failing with "release version 21 not supported". Bump the job to JDK 21, matching the Maven workflows (which already build against 21). The engine and the Gradle plugin both require Java 21. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Enum fields bypassed processObjectProperty's applyMetadata, so their schema `description`/`example` were dropped from the generated @Schema annotation. Set them in processEnumField so enum properties match the rest. Bumps version 6.5.1 -> 6.5.2. Full multiapi-engine suite: 110/110 (mvn clean test). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
OpenAPI 3.x / JSON Schema `deprecated: true` on a property (or enum) is now carried into the generated model as @Schema(deprecated = true); previously it was ignored. Applied at the same property/enum metadata points as description/example. Bumps version 6.5.2 -> 6.5.3. Full multiapi-engine suite: 110/110 (mvn clean test). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
joseegman-idoneea
force-pushed
the
feat/openapi31-deprecated
branch
from
July 24, 2026 10:17
6a85a07 to
7e827c9
Compare
joseegman-idoneea
changed the title
jemacineiras
approved these changes
Jul 24, 2026
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
2 participants
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.
Follow-up to #383 (merged as 6.5.1 with the Maven Central publish fix). #383's squash merge captured only its first commit, so the Gradle release CI fix did not land — this PR restores it and adds two more OpenAPI 3.1 refinements. Cuts 6.5.3.
Release-blocking fix (missing from main)
gradle-portal-pushworkflow set up JDK 17 but runsmvn installon the engine (compiled withrelease 21) → fails with "release version 21 not supported". Bumped to JDK 21, matching the Maven workflows.OpenAPI 3.1 refinements
description/example/examplesnow propagate to enum fields (they bypassed the metadata step).deprecated: trueon a property or enum is emitted as@Schema(deprecated = true)(was ignored).Version
6.5.1→6.5.3(engine, Maven plugin, Gradle plugin). Central versions are immutable, so a fresh number is required to re-publish.Verification
Full
multiapi-enginesuite: 110/110 (mvn clean test).🤖 Generated with Claude Code