chore: version packages - #32
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 14:23
13754dc to
469be80
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 19:31
469be80 to
7a29ab7
Compare
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@sailpoint/ui-plugin-sdk@0.1.0
Minor Changes
e2d78dc: Align plugin context types with the App Shell capability-flag contract (CSTM-354).
Breaking. App Shell now sends an exhaustive map of public capability booleans
instead of fine-grained rights, so the SDK's context declarations were not just
stale but actively wrong:
capabilities?: string[]compiled cleanly against avalue that is really an object, then threw
TypeError: ...includes is not a functionat runtime.UserContext.capabilitiesis now a requiredUserCapabilitiesobject with all13 flags. Replace
capabilities?.includes('ORG_ADMIN')withcapabilities.isOrgAdmin.amsRights,uiRights,uid,alias,lastLoginTimestamp,federated, andmfeSessionHashfromUserContext— App Shell never sent them.TenantContext.name,pod,region,apiUrl, andproductsare nowrequired,
productsis typedTenantProduct[]withlicenses, andTenantApiUrlis narrowed to exactly{ idn: string }.[key: string]: unknownindex signatures fromTenantContext,UserContext,PageContext, andTenantApiUrl, so a misspelled field is acompile error instead of
unknown.PluginContext.pluginConfiguration, exposing theslotConfigurationandpluginIdthe SDK previously discarded.HANDSHAKE_FAILEDwhen the host payload does not match, rather than handingplugins
undefinedat a site the types call safe.api.get/api.postno longer derive a hostname from the tenant name whenapiUrlis absent; they use the validatedtenant.apiUrl.idn.UserCapabilities,CapabilityFlagKey,TenantProduct,TenantProductLicense,PluginConfiguration,SlotConfiguration,TenantApiUrl.Requires App Shell at
saas-sp-renderer@4100daeaor later.