fix(Context-Based Restrictions): add display name to service ref response#313
Merged
fix(Context-Based Restrictions): add display name to service ref response#313
Conversation
Signed-off-by: Dylan <Dylan.Yu@ibm.com>
Signed-off-by: Dylan <Dylan.Yu@ibm.com>
|
|
pyrooka
changed the title
Contributor
Author
|
Integration test Examples |
ibm-devx-sdk
pushed a commit
that referenced
this pull request
Jan 15, 2026
## [0.73.1](v0.73.0...v0.73.1) (2026-01-15) ### Bug Fixes * **Context-Based Restrictions:** add display name to service ref response ([#313](#313)) ([d3d7f8c](d3d7f8c))
|
🎉 This PR is included in version 0.73.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
4 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.
PR summary
Adding missing property to service ref response
Also, auto-generation has a lot of cleanliness changes, going ahead and applying now to avoid future efforts.
PR Checklist
Please make sure that your PR fulfills the following requirements:
Current vs new behavior
Added display name to service ref response. No service should be dependent on it, but it is nice to have.
Does this PR introduce a breaking change?