feat: access control segmentation #62
Merged
Conversation
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
BREAKING CHANGE: ScopeID is now required to create a new profile attachment Signed-off-by: Bryan Bosely <bbosely@us.ibm.com>
tyao117
approved these changes
Apr 21, 2025
sccibm
pushed a commit
that referenced
this pull request
Apr 21, 2025
# [5.0.0](v4.0.1...v5.0.0) (2025-04-21) ### Features * access control segmentation ([fbc915c](fbc915c)) * access control segmentation ([7fb9dae](7fb9dae)) * access control segmentation ([#62](#62)) ([f7e9e2d](f7e9e2d)) * access control segmentation ([#65](#65)) ([a7f6d69](a7f6d69)) ### BREAKING CHANGES * ScopeID is now required to create a new profile attachment Signed-off-by: Bryan Bosely <bbosely@us.ibm.com> * ScopeID is now required to create a new profile attachment Signed-off-by: Bryan Bosely <bbosely@us.ibm.com>
Collaborator
|
🎉 This PR is included in version 5.0.0 🎉 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.
BREAKING CHANGE: ScopeID is now required to create a new profile attachment
PR summary
Force release 5.0.0 of SDK
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