[TT-12312] update openapi spec version#6323
Merged
Merged
Conversation
lghiur
approved these changes
Jun 6, 2024
Contributor
PR Review 🔍
Code feedback: |
Contributor
|
API Changes no api changes detected |
Contributor
PR Code Suggestions ✨
|
jeffy-mathew
enabled auto-merge (squash)
June 6, 2024 12:04
|
Contributor
Author
|
/release to release-5.4 |
Contributor
Author
|
/release to release-5.4.0 |
|
Working on it! Note that it can take a few minutes. |
1 similar comment
|
Working on it! Note that it can take a few minutes. |
tykbot Bot
pushed a commit
that referenced
this pull request
Jun 6, 2024
### **User description** <!-- Provide a general summary of your changes in the Title above --> ## Description Update version in openapi spec. ## Related Issue https://tyktech.atlassian.net/browse/TT-12312 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why ___ ### **PR Type** enhancement, documentation ___ ### **Description** - Updated the OpenAPI specification version from 5.3.0 to 5.4.0 in the `swagger.yml` file. - Ensured the documentation reflects the latest API version for better integration and automation. ___ ### **Changes walkthrough** 📝 <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Enhancement </strong></td><td><table> <tr> <td> <details> <summary><strong>swagger.yml</strong><dd><code>Update OpenAPI spec version to 5.4.0</code> </dd></summary> <hr> swagger.yml - Updated the OpenAPI spec version from 5.3.0 to 5.4.0. </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6323/files#diff-8f3c4cb253eee09ae2401daa7279a8bbfbfd4168bb579c3ac0ee5c672d63bb2c">+1/-1</a> </td> </tr> </table></td></tr></tr></tbody></table> ___ > 💡 **PR-Agent usage**: >Comment `/help` on the PR to get a list of all available PR-Agent tools and their descriptions (cherry picked from commit 874f470)
7 tasks
|
@jeffy-mathew Succesfully merged PR |
tykbot Bot
pushed a commit
that referenced
this pull request
Jun 6, 2024
### **User description** <!-- Provide a general summary of your changes in the Title above --> ## Description Update version in openapi spec. ## Related Issue https://tyktech.atlassian.net/browse/TT-12312 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why ___ ### **PR Type** enhancement, documentation ___ ### **Description** - Updated the OpenAPI specification version from 5.3.0 to 5.4.0 in the `swagger.yml` file. - Ensured the documentation reflects the latest API version for better integration and automation. ___ ### **Changes walkthrough** 📝 <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Enhancement </strong></td><td><table> <tr> <td> <details> <summary><strong>swagger.yml</strong><dd><code>Update OpenAPI spec version to 5.4.0</code> </dd></summary> <hr> swagger.yml - Updated the OpenAPI spec version from 5.3.0 to 5.4.0. </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6323/files#diff-8f3c4cb253eee09ae2401daa7279a8bbfbfd4168bb579c3ac0ee5c672d63bb2c">+1/-1</a> </td> </tr> </table></td></tr></tr></tbody></table> ___ > 💡 **PR-Agent usage**: >Comment `/help` on the PR to get a list of all available PR-Agent tools and their descriptions (cherry picked from commit 874f470)
7 tasks
|
@jeffy-mathew Succesfully merged PR |
buger
added a commit
that referenced
this pull request
Jun 6, 2024
[TT-12312] update openapi spec version (#6323) ### **User description** <!-- Provide a general summary of your changes in the Title above --> ## Description Update version in openapi spec. ## Related Issue https://tyktech.atlassian.net/browse/TT-12312 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why ___ ### **PR Type** enhancement, documentation ___ ### **Description** - Updated the OpenAPI specification version from 5.3.0 to 5.4.0 in the `swagger.yml` file. - Ensured the documentation reflects the latest API version for better integration and automation. ___ ### **Changes walkthrough** 📝 <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Enhancement </strong></td><td><table> <tr> <td> <details> <summary><strong>swagger.yml</strong><dd><code>Update OpenAPI spec version to 5.4.0</code> </dd></summary> <hr> swagger.yml - Updated the OpenAPI spec version from 5.3.0 to 5.4.0. </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6323/files#diff-8f3c4cb253eee09ae2401daa7279a8bbfbfd4168bb579c3ac0ee5c672d63bb2c">+1/-1</a> </td> </tr> </table></td></tr></tr></tbody></table> ___ > 💡 **PR-Agent usage**: >Comment `/help` on the PR to get a list of all available PR-Agent tools and their descriptions
buger
added a commit
that referenced
this pull request
Jun 6, 2024
[TT-12312] update openapi spec version (#6323) ### **User description** <!-- Provide a general summary of your changes in the Title above --> ## Description Update version in openapi spec. ## Related Issue https://tyktech.atlassian.net/browse/TT-12312 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why ___ ### **PR Type** enhancement, documentation ___ ### **Description** - Updated the OpenAPI specification version from 5.3.0 to 5.4.0 in the `swagger.yml` file. - Ensured the documentation reflects the latest API version for better integration and automation. ___ ### **Changes walkthrough** 📝 <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Enhancement </strong></td><td><table> <tr> <td> <details> <summary><strong>swagger.yml</strong><dd><code>Update OpenAPI spec version to 5.4.0</code> </dd></summary> <hr> swagger.yml - Updated the OpenAPI spec version from 5.3.0 to 5.4.0. </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6323/files#diff-8f3c4cb253eee09ae2401daa7279a8bbfbfd4168bb579c3ac0ee5c672d63bb2c">+1/-1</a> </td> </tr> </table></td></tr></tr></tbody></table> ___ > 💡 **PR-Agent usage**: >Comment `/help` on the PR to get a list of all available PR-Agent tools and their descriptions
nerdydread
pushed a commit
that referenced
this pull request
Sep 6, 2024
### **User description** <!-- Provide a general summary of your changes in the Title above --> ## Description Update version in openapi spec. ## Related Issue https://tyktech.atlassian.net/browse/TT-12312 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why ___ ### **PR Type** enhancement, documentation ___ ### **Description** - Updated the OpenAPI specification version from 5.3.0 to 5.4.0 in the `swagger.yml` file. - Ensured the documentation reflects the latest API version for better integration and automation. ___ ### **Changes walkthrough** 📝 <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Enhancement </strong></td><td><table> <tr> <td> <details> <summary><strong>swagger.yml</strong><dd><code>Update OpenAPI spec version to 5.4.0</code> </dd></summary> <hr> swagger.yml - Updated the OpenAPI spec version from 5.3.0 to 5.4.0. </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6323/files#diff-8f3c4cb253eee09ae2401daa7279a8bbfbfd4168bb579c3ac0ee5c672d63bb2c">+1/-1</a> </td> </tr> </table></td></tr></tr></tbody></table> ___ > 💡 **PR-Agent usage**: >Comment `/help` on the PR to get a list of all available PR-Agent tools and their descriptions
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.
User description
Description
Update version in openapi spec.
Related Issue
https://tyktech.atlassian.net/browse/TT-12312
Motivation and Context
How This Has Been Tested
Screenshots (if appropriate)
Types of changes
Checklist
PR Type
enhancement, documentation
Description
swagger.ymlfile.Changes walkthrough 📝
swagger.yml
Update OpenAPI spec version to 5.4.0swagger.yml