Merge branch 'master' into fork/damiankaplon/refs-enum

Author: ewaostrowska

.github/ISSUE_TEMPLATE/01_bug_report.md

@@ -0,0 +1,59 @@
+---
+name: Bug Report
+about: Report an issue in swagger-core
+title: "[Bug]: "
+labels: Bug
+assignees: ''
+---
+
+## Description of the problem/issue
+
+<!--
+Provide a clear and concise description of the problem.
+To help us understand the issue better, consider including:
+- What are you trying to achieve using swagger-core?
+- Are specific annotations not behaving as expected? (e.g., @Schema, @Parameter, @Operation)
+- Are generated OpenAPI specs missing information or incorrect?
+- Are you using swagger-core with JAX-RS, Spring, or another framework?
+- Did this issue affect code generation (e.g., Swagger Codegen/OpenAPI Generator)?
+-->
+
+## Affected Version
+
+<!-- What version of swagger-core are you using? -->
+e.g. 2.2.21
+
+<!-- Can you identify when the issue was introduced?
+If yes, please provide the earliest version you know the bug exists in. -->
+Earliest version the bug appears in (if known):  
+e.g. 2.2.17
+
+## Steps to Reproduce
+
+<!-- Provide a step-by-step list on how to reproduce the issue.
+Include any relevant OpenAPI definitions, configuration, or code snippets. -->
+
+1. ...
+2. ...
+3. ...
+
+## Expected Behavior
+
+<!-- What should have happened? -->
+
+## Actual Behavior
+
+<!-- What actually happened instead? -->
+
+## Logs / Stack Traces
+
+<!-- Paste relevant log output or error messages, if any. -->
+
+## Additional Context
+
+<!-- Add any other context, links, or screenshots about the problem here. -->
+
+## Checklist
+
+- [ ] I have searched the [existing issues](https://github.com/swagger-api/swagger-core/issues) and this is not a duplicate.
+- [ ] I have provided sufficient information for maintainers to reproduce the issue.

.github/ISSUE_TEMPLATE/02_question.md

@@ -0,0 +1,43 @@
+---
+name: Question
+about: Ask a question about swagger-core usage or behavior
+title: "[Question]: "
+labels: Question
+assignees: ''
+---
+
+## Question
+
+<!--
+Please clearly describe your question or the problem you're trying to solve.
+To help us answer faster, consider including:
+- What are you trying to achieve with swagger-core?
+- Which version are you using?
+- What have you tried so far?
+- Are you encountering unexpected behavior or error messages?
+-->
+
+## Affected Version
+
+<!-- What version of swagger-core are you using? -->
+e.g. 2.2.21
+
+## Context
+
+<!--
+Provide any relevant code snippets, configuration, OpenAPI definitions,
+or links to documentation you are referring to.
+-->
+
+```java
+// Example code snippet here
+```
+
+## Additional Details
+
+<!-- Add any other information that might help us understand your question. -->
+
+## Checklist
+
+- [ ] I have searched the [existing issues](https://github.com/swagger-api/swagger-core/issues) and documentation before asking.
+- [ ] I have provided enough information for others to understand my question.

.github/ISSUE_TEMPLATE/03_feature_request.md

@@ -0,0 +1,50 @@
+---
+name: Feature Request
+about: Suggest a new feature or enhancement for swagger-core
+title: "[Feature]: "
+labels: Feature
+assignees: ''
+---
+
+## Feature Description
+
+<!--
+Describe the feature you'd like to see.
+- What problem does it solve?
+- How would it improve swagger-core?
+- Is it related to OpenAPI spec support, annotation improvements, integration, etc.?
+-->
+
+## Use Case
+
+<!--
+Explain how you (or others) would use this feature in a real-world project.
+Include context to help understand why this is valuable.
+-->
+
+## Suggested Solution (optional)
+
+<!--
+If you have an idea for how the feature could be implemented, share it here.
+This could include proposed APIs, annotations, or behavior.
+-->
+
+## Alternatives Considered
+
+<!--
+Have you tried other ways to solve this problem?
+Are there any existing workarounds?
+-->
+
+## Additional Context
+
+<!--
+Include any other information, references, or related issues.
+Screenshots, links to OpenAPI specs, or code snippets can help too.
+-->
+
+## Checklist
+
+- [ ] I have searched the [existing issues](https://github.com/swagger-api/swagger-core/issues) to ensure this is not a duplicate.
+- [ ] This feature would be useful to more than just my use case.
+- [ ] I have provided enough detail for the maintainers to understand the scope of the request.

.github/pull_request_template.md

@@ -0,0 +1,43 @@
+# Pull Request
+
+Thank you for contributing to **swagger-core**!
+
+Please fill out the following information to help us review your PR efficiently.
+
+---
+
+## Description
+
+<!--
+Describe what this PR changes:
+- What problem does it solve?
+- Is it a bug fix, new feature, or refactor?
+- Link to any related issues.
+-->
+
+Fixes: <!-- e.g. #123 (optional) -->
+
+## Type of Change
+
+<!-- Check all that apply: -->
+
+- [ ] 🐛 Bug fix
+- [ ] ✨ New feature
+- [ ] ♻️ Refactor (non-breaking change)
+- [ ] 🧪 Tests
+- [ ] 📝 Documentation
+- [ ] 🧹 Chore (build or tooling)
+
+## Checklist
+
+<!-- Please check all that apply before requesting review: -->
+
+- [ ] I have added/updated tests as needed
+- [ ] I have added/updated documentation where applicable
+- [ ] The PR title is descriptive
+- [ ] The code builds and passes tests locally
+- [ ] I have linked related issues (if any)
+
+## Screenshots / Additional Context
+
+<!-- Optional: Add logs, screenshots, or notes for reviewers -->

README.md

@@ -23,7 +23,8 @@ The OpenAPI Specification has undergone several revisions since initial creation
 
 Swagger core Version      | Release Date | OpenAPI Spec compatibility | Notes | Status
 ------------------------- | ------------ | -------------------------- | ----- | ----
-2.2.34 (**current stable**)| 2025-06-20   | 3.x           | [tag v2.2.34](https://github.com/swagger-api/swagger-core/tree/v2.2.34) | Supported
+2.2.35 (**current stable**)| 2025-07-31   | 3.x           | [tag v2.2.35](https://github.com/swagger-api/swagger-core/tree/v2.2.35) | Supported
+2.2.34                     | 2025-06-20   | 3.x           | [tag v2.2.34](https://github.com/swagger-api/swagger-core/tree/v2.2.34) | Supported
 2.2.33                     | 2025-06-12   | 3.x           | [tag v2.2.33](https://github.com/swagger-api/swagger-core/tree/v2.2.33) | Supported
 2.2.32                     | 2025-05-14   | 3.x           | [tag v2.2.32](https://github.com/swagger-api/swagger-core/tree/v2.2.32) | Supported
 2.2.31                     | 2025-05-13   | 3.x           | [tag v2.2.31](https://github.com/swagger-api/swagger-core/tree/v2.2.31) | Supported
@@ -127,7 +128,7 @@ You need the following installed and available in your $PATH:
 * Jackson 2.4.5 or greater
 
 
-### To build from source (currently 2.2.35-SNAPSHOT)
+### To build from source (currently 2.2.36-SNAPSHOT)
 ```
 # first time building locally
 mvn -N

modules/swagger-annotations/pom.xml

@@ -3,7 +3,7 @@
     <parent>
         <groupId>io.swagger.core.v3</groupId>
         <artifactId>swagger-project</artifactId>
-        <version>2.2.35-SNAPSHOT</version>
+        <version>2.2.36-SNAPSHOT</version>
         <relativePath>../..</relativePath>
     </parent>
     <modelVersion>4.0.0</modelVersion>

modules/swagger-core/pom.xml

@@ -3,7 +3,7 @@
     <parent>
         <groupId>io.swagger.core.v3</groupId>
         <artifactId>swagger-project</artifactId>
-        <version>2.2.35-SNAPSHOT</version>
+        <version>2.2.36-SNAPSHOT</version>
         <relativePath>../..</relativePath>
     </parent>
     <modelVersion>4.0.0</modelVersion>

modules/swagger-eclipse-transformer-maven-plugin/pom.xml

@@ -4,7 +4,7 @@
     <parent>
         <groupId>io.swagger.core.v3</groupId>
         <artifactId>swagger-project</artifactId>
-        <version>2.2.35-SNAPSHOT</version>
+        <version>2.2.36-SNAPSHOT</version>
         <relativePath>../..</relativePath>
     </parent>
     <modelVersion>4.0.0</modelVersion>

modules/swagger-gradle-plugin/README.md

@@ -14,7 +14,7 @@ In many cases it is sufficient to set it to the `classpath` value, like:
 
 Alternatively provide as value a classpath with the following dependencies (replacing the provided [`javax` ones](https://github.com/swagger-api/swagger-core/blob/master/modules/swagger-gradle-plugin/src/main/java/io/swagger/v3/plugins/gradle/SwaggerPlugin.java#L16-L25)):
 
-* org.apache.commons:commons-lang3:3.12.0
+* org.apache.commons:commons-lang3:3.18.0
 * io.swagger.core.v3:swagger-jaxrs2-jakarta:2.2.9
 * jakarta.ws.rs:jakarta.ws.rs-api:3.0.0
 * jakarta.servlet:jakarta.servlet-api:5.0.0
@@ -26,7 +26,7 @@ Alternatively provide as value a classpath with the following dependencies (repl
 
 ```
 plugins {
-  id "io.swagger.core.v3.swagger-gradle-plugin" version "2.2.34"
+  id "io.swagger.core.v3.swagger-gradle-plugin" version "2.2.35"
 }
 ```
 ### Gradle 1.x and 2.0
@@ -43,7 +43,7 @@ buildscript {
     }
   }
   dependencies {
-    classpath "io.swagger.core.v3:swagger-gradle-plugin:2.2.34"
+    classpath "io.swagger.core.v3:swagger-gradle-plugin:2.2.35"
   }
 }
 
@@ -123,14 +123,13 @@ info:
     url: http://www.apache.org/licenses/LICENSE-2.0.html
 ```
 
-Since version 2.1.6, `sortOutput` parameter is available, allowing to sort object properties and map keys alphabetically.
-Since version 2.1.6, `objectMapperProcessorClass` allows to configure also the ObjectMapper instance used to serialize the resolved OpenAPI
-Since version 2.1.9, `alwaysResolveAppPath` parameter is available, allowing to trigger resolving of Application Path from annotation also not in runtime (e.g. using servlet in separate application, or in maven plugin at build time, etc)
-Since version 2.2.12, `openapi31` parameter is available, if set to true the resolved spec will be processed into a 3.1.0 specification by resolving according to OAS 3.1 rules
-Since version 2.1.15, `skipResolveAppPath` parameter is available, allowing to skip resolving of Application Path from annotation
-Since version 2.2.17, `defaultResponseCode` parameter is available, allowing to set the code used when resolving responses with no http status code annotation
-Since version 2.2.17, `defaultResponseCode` parameter is available, allowing to set the code used when resolving responses with no http status code annotation
-Since version 2.2.24, `schemaResolution` parameter is available, allowing to specify how object schemas and object properties within schemas are resolved for OAS 3.0 specification
-Since version 2.2.28, `openAPIVersion` parameter is available, allowing to specify the version of the OpenAPI specification to be used for the resolved spec.
-Since version 2.2.29, `groupsValidationStrategy` parameter is available, allowing to specify the strategy for resolving Validation annotations (`never`, `always`, `neverIfNoContext`).
-Since version 2.2.29, `validatorProcessorClass` parameter is available, allowing to specify a custom validator processor class, implementation of `io.swagger.v3.core.util.ValidatorProcessor`.
+- Since version 2.1.6, `sortOutput` parameter is available, allowing to sort object properties and map keys alphabetically.
+- Since version 2.1.6, `objectMapperProcessorClass` allows to configure also the ObjectMapper instance used to serialize the resolved OpenAPI
+- Since version 2.1.9, `alwaysResolveAppPath` parameter is available, allowing to trigger resolving of Application Path from annotation also not in runtime (e.g. using servlet in separate application, or in maven plugin at build time, etc)
+- Since version 2.2.12, `openapi31` parameter is available, if set to true the resolved spec will be processed into a 3.1.0 specification by resolving according to OAS 3.1 rules
+- Since version 2.1.15, `skipResolveAppPath` parameter is available, allowing to skip resolving of Application Path from annotation
+- Since version 2.2.17, `defaultResponseCode` parameter is available, allowing to set the code used when resolving responses with no http status code annotation
+- Since version 2.2.24, `schemaResolution` parameter is available, allowing to specify how object schemas and object properties within schemas are resolved for OAS 3.0 specification
+- Since version 2.2.28, `openAPIVersion` parameter is available, allowing to specify the version of the OpenAPI specification to be used for the resolved spec.
+- Since version 2.2.29, `groupsValidationStrategy` parameter is available, allowing to specify the strategy for resolving Validation annotations (`never`, `always`, `neverIfNoContext`).
+- Since version 2.2.29, `validatorProcessorClass` parameter is available, allowing to specify a custom validator processor class, implementation of `io.swagger.v3.core.util.ValidatorProcessor`.

modules/swagger-gradle-plugin/build.gradle

@@ -24,7 +24,7 @@ compileJava {
 
 dependencies {
     implementation gradleApi()
-    implementation 'org.apache.commons:commons-lang3:3.14.0'
+    implementation 'org.apache.commons:commons-lang3:3.18.0'
 
     testImplementation gradleTestKit()
     testImplementation('com.github.tomakehurst:wiremock:2.27.2') {