chore(swagger-bugfix): refactor workflow to resolve release version tag issue #295
Conversation
This file contains 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
saudkhan116
added
bug
matbmoser
approved these changes
Apr 24, 2024
saudkhan116
force-pushed
the
bugfix/fix-swagger-workflow
branch
from
e5d7356
to
febe535
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why we create this PR?
Problem Statement
The swagger workflow had a bug that it didn't redirect to the latest release tag e.g.,
2.2.0by default once a new released is published and swagger is accessible from the link https://app.swaggerhub.com/apis/eclipse-tractusx-bot/digital-product-passThis PR contains the following changes:
What we want to achieve with this PR?
Expected Behavior
To trigger the workflow and publish OpenAPI specs through central swaggerhub https://app.swaggerhub.com/apis/eclipse-tractusx-bot/digital-product-pass once a new release is published. The API specs must access the new published version of release tag by default.
What is new?
Updated
Fixed Issues
Linked Issue(s):
#279