fix(Catalog Management): re-gen after operation name changes #87
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
JonWoodlief
force-pushed
the
catmgmt-update
branch
2 times, most recently
from
a1af04e to
737ac62
Compare
padamstx
force-pushed
the
catmgmt-update
branch
from
737ac62 to
b2d34f2
Compare
dubee
approved these changes
Feb 23, 2021
ibm-devx-automation
pushed a commit
that referenced
this pull request
Feb 23, 2021
## [0.17.13](v0.17.12...v0.17.13) (2021-02-23) ### Bug Fixes * **Catalog Management:** re-gen after operation name changes ([#87](#87)) ([1718555](1718555))
|
🎉 This PR is included in version 0.17.13 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
PR summary
This PR contains a re-gen of the Catalog Management service after changes to some operation names.
PR Checklist
Please make sure that your PR fulfills the following requirements:
Current vs new behavior
Does this PR introduce a breaking change?
Other information