Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merging to release-5.3.8: Tt 13476 update gw oas version (#6692) #6695

Conversation

buger
Copy link
Member

@buger buger commented Nov 7, 2024

User description

Tt 13476 update gw oas version (#6692)

https://github.com/TykTechnologies/tyk-analytics/pull/4281/files

Description

Updates gateway OpenAPI version

Related Issue

Motivation and Context

How This Has Been Tested

Screenshots (if appropriate)

Types of changes

  • 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

  • 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


Description

  • Updated the OpenAPI version in the swagger.yml file from 5.3.0 to 5.3.8 to reflect the latest changes in the Tyk Gateway API.

Changes walkthrough 📝

Relevant files
Enhancement
swagger.yml
Update OpenAPI version in `swagger.yml` to 5.3.8                 

swagger.yml

  • Updated the OpenAPI version from 5.3.0 to 5.3.8.
+1/-1     

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

https://github.com/TykTechnologies/tyk-analytics/pull/4281/files

## Description

Updates gateway OpenAPI version 

## Related Issue

<!-- This project only accepts pull requests related to open issues. -->
<!-- If suggesting a new feature or change, please discuss it in an
issue first. -->
<!-- If fixing a bug, there should be an issue describing it with steps
to reproduce. -->
<!-- OSS: Please link to the issue here. Tyk: please create/link the
JIRA ticket. -->

## 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

(cherry picked from commit 58911f4)
@buger buger enabled auto-merge (squash) November 7, 2024 09:30
Copy link
Contributor

github-actions bot commented Nov 7, 2024

API Changes

no api changes detected

Copy link
Contributor

github-actions bot commented Nov 7, 2024

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅

6692 - Fully compliant

Fully compliant requirements:

  • Update the OpenAPI version in the swagger.yml file to reflect the latest changes in the Tyk Gateway API.
⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ No major issues detected

Copy link
Contributor

github-actions bot commented Nov 7, 2024

PR Code Suggestions ✨

No code suggestions found for the PR.

Copy link

sonarqubecloud bot commented Nov 7, 2024

@buger buger merged commit 8cc37bf into release-5.3.8 Nov 7, 2024
35 of 37 checks passed
@buger buger deleted the merge/release-5.3.8/58911f4d8c757faeabcf84b8f069bfdbc7709187 branch November 7, 2024 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants