[KOTLIN-SPRING;JAVA-SPRING] chore: upgrade spring boot 3 to 3.3.13 version

[Picazsoo]

Upgraded spring boot 3 version to 3.3.13

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in WSL)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request. - @cachescrubber (2022/02) @welshm (2022/02) @MelleD (2022/02) @atextor (2022/02) @manedev79 (2022/02) @javisst (2022/02) @borsch (2022/02) @banlevente (2022/02) @Zomzog (2022/09) @martin-mfg (2023/08), @karismann (2019/03) @Zomzog (2019/04) @andrewemery (2019/10) @4brunu (2019/11) @yutaka0m (2020/03) @stefankoppier (2022/06) @e5l (2024/10) @dennisameling (2026/02)

---

Summary by cubic

Upgrade Kotlin and Java Spring generator templates and petstore samples to Spring Boot 3.3.13 and Spring Cloud 2023.0.6. Modernizes OAuth2 for Spring Boot 3 and aligns Gradle/Maven builds.

• Dependencies

  • Spring Boot: Gradle org.springframework.boot 3.0.2 -> 3.3.13; Maven spring-boot-starter-parent 3.1.3 -> 3.3.13.
  • Spring Cloud: BOM/parent spring-cloud-dependencies/spring-cloud-starter-parent 2021.0.5/2023.0.0 -> 2023.0.6.
  • Gradle: io.spring.dependency-management 1.0.14.RELEASE -> 1.1.7.
  • OAuth: replace org.springframework.cloud:spring-cloud-starter-oauth2:2.2.5.RELEASE with org.springframework.boot:spring-boot-starter-oauth2-client.

• Refactors

  • Add Spring Boot 3 OAuth2 Feign interceptor using OAuth2AuthorizedClientManager in ClientConfiguration, with per-flow beans toggled by spring.security.oauth2.client.registration.{name}{Flow}.enabled=true.

^{Written for commit 49a3262. Summary will update on new commits.}

[cubic-dev-ai]

10 issues found across 28 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="modules/openapi-generator/src/main/resources/kotlin-spring/libraries/spring-declarative-http-interface/buildGradle-sb3-Kts.mustache">

<violation number="1" location="modules/openapi-generator/src/main/resources/kotlin-spring/libraries/spring-declarative-http-interface/buildGradle-sb3-Kts.mustache:21">
P1: Spring Boot was upgraded to 3.3.13 but Spring Cloud coordinates remain on older 2021.x/2.2.x-era versions, creating an incompatible dependency baseline.</violation>
</file>

<file name="samples/server/petstore/kotlin-spring-declarative-interface-reactive-reactor-wrapped/build.gradle.kts">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface-reactive-reactor-wrapped/build.gradle.kts:21">
P1: Spring Boot was upgraded to 3.3.13 without upgrading Spring Cloud BOM/starter versions to a compatible release train.</violation>
</file>

<file name="modules/openapi-generator/src/main/resources/kotlin-spring/libraries/spring-cloud/buildGradle-sb3-Kts.mustache">

<violation number="1" location="modules/openapi-generator/src/main/resources/kotlin-spring/libraries/spring-cloud/buildGradle-sb3-Kts.mustache:21">
P1: Spring Boot was upgraded to 3.3.13 but Spring Cloud BOM remains at 2021.0.5, which is not aligned with Boot 3.3.x.</violation>
</file>

<file name="modules/openapi-generator/src/main/resources/kotlin-spring/libraries/spring-cloud/pom-sb3.mustache">

<violation number="1" location="modules/openapi-generator/src/main/resources/kotlin-spring/libraries/spring-cloud/pom-sb3.mustache:30">
P1: Boot was upgraded to 3.3.13 but Spring Cloud BOM remained at 2021.0.5, creating a release-train compatibility mismatch for generated projects.</violation>
</file>

<file name="samples/server/petstore/kotlin-spring-declarative-interface-wrapped/pom.xml">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface-wrapped/pom.xml:20">
P1: Spring Boot was upgraded to 3.3.13 without upgrading Spring Cloud train/dependencies, creating a supported-version mismatch.</violation>
</file>

<file name="samples/server/petstore/kotlin-spring-declarative-interface/build.gradle.kts">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface/build.gradle.kts:21">
P1: Upgrading to Spring Boot 3.3.13 while keeping Spring Cloud 2021.0.5 / old Cloud OAuth starter creates an unsupported dependency combination.</violation>
</file>

<file name="samples/server/petstore/kotlin-spring-declarative-interface-reactive-coroutines/pom.xml">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface-reactive-coroutines/pom.xml:22">
P1: Spring Boot was upgraded to 3.3.13 without aligning the Spring Cloud release train, leaving an unsupported dependency platform combination.</violation>
</file>

<file name="modules/openapi-generator/src/main/resources/kotlin-spring/libraries/spring-boot/buildGradle-sb3-Kts.mustache">

<violation number="1" location="modules/openapi-generator/src/main/resources/kotlin-spring/libraries/spring-boot/buildGradle-sb3-Kts.mustache:27">
P1: Spring Boot was upgraded to 3.3.13 but dependency-management remains pinned to old 1.0.14, causing risky plugin-version skew and potential Gradle compatibility issues.</violation>
</file>

<file name="samples/server/petstore/kotlin-spring-declarative-interface/pom.xml">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface/pom.xml:20">
P1: Upgrading to Spring Boot 3.3.13 without aligning Spring Cloud versions creates an unsupported dependency mix likely to break compatibility.</violation>
</file>

<file name="samples/server/petstore/kotlin-spring-declarative-interface-wrapped/build.gradle.kts">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface-wrapped/build.gradle.kts:21">
P1: Spring Boot was upgraded to 3.3.13, but Spring Cloud dependencies remain on legacy versions, creating a likely compatibility mismatch.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

4 issues found across 27 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="samples/server/petstore/kotlin-spring-declarative-interface/build.gradle.kts">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface/build.gradle.kts:35">
P2: Upgrading to Spring Cloud BOM 2023.0.9 while pinning `spring-cloud-starter-oauth2:2.2.5.RELEASE` creates a cross-generation dependency mismatch likely incompatible with Boot 3/Jakarta stack.</violation>
</file>

<file name="samples/server/petstore/kotlin-spring-declarative-interface-reactive-coroutines/build.gradle.kts">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface-reactive-coroutines/build.gradle.kts:35">
P1: Upgrading to Spring Cloud BOM 2023.0.9 while keeping legacy `spring-cloud-starter-oauth2:2.2.5.RELEASE` introduces a likely incompatible dependency mix for Boot 3.x.</violation>
</file>

<file name="samples/server/petstore/kotlin-spring-declarative-interface-wrapped/build.gradle.kts">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface-wrapped/build.gradle.kts:35">
P1: Spring Cloud BOM was upgraded to 2023.x, but an explicit legacy `spring-cloud-starter-oauth2:2.2.5.RELEASE` remains, creating a likely incompatible dependency line in a Boot 3/Jakarta project.</violation>
</file>

<file name="samples/server/petstore/kotlin-spring-declarative-interface-reactive-reactor-wrapped/build.gradle.kts">

<violation number="1" location="samples/server/petstore/kotlin-spring-declarative-interface-reactive-reactor-wrapped/build.gradle.kts:35">
P1: Upgrading to Spring Cloud BOM 2023.0.9 while keeping `spring-cloud-starter-oauth2:2.2.5.RELEASE` introduces a legacy/new dependency-line mismatch that can cause Boot 3.x classpath incompatibilities.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[wing328]

thanks for the PR which has been merged