-
Notifications
You must be signed in to change notification settings - Fork 44
fix(Context-Based Restrictions): add display name to service ref response #290
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
Conversation
Signed-off-by: Dylan <Dylan.Yu@ibm.com>
35c3bc0 to
b8fe866
Compare
pyrooka
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you need to rebase this PR onto the main branch. If you look at the commits you can see 3 that don't belong here: 2 release commits and one for the IAM Identity service. Please remove those from this PR just to make sure we won't mess up anything - even though it shouldn't cause an issue.
7dad793 to
d46a7f9
Compare
pyrooka
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
## [0.73.1](0.73.0...0.73.1) (2026-01-15) ### Bug Fixes * **Context-Based Restrictions:** add display name to service ref response ([#290](#290)) ([dd2444e](dd2444e))
|
🎉 This PR is included in version 0.73.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |




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?