feat(hub-common): modified sharing level access on site sharing level #2011
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
…level itself affects: @esri/hub-common
affects: @esri/hub-common
affects: @esri/hub-common
…t exceeds site access affects: @esri/hub-common
affects: @esri/hub-common
affects: @esri/hub-common
DavidSpriggs
deleted the
t/14115-update-site-workspace-assistant-configuration
branch
esri-dcdev-2
pushed a commit
that referenced
this pull request
Sep 26, 2025
# @esri/hub-common [20.12.0](https://github.com/Esri/hub.js/compare/@esri/[email protected]...@esri/[email protected]) (2025-09-26) ### Features * **hub-common:** modified sharing level access on site sharing level ([#2011](#2011)) ([21888a9](21888a9))
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.
Modified sharing level access on the hub-ai assistant
Related to https://devtopia.esri.com/dc/hub/issues/14115
Updated meaningful TSDoc to methods including Parameters and Returns, see Documentation Guide
used semantic commit messages
PR title follows semantic commit format (CRITICAL if the title is not in a semantic format, the release automation will not run!)
Updated
peerDependenciesas needed. CRITICAL our automated release system can not be counted on to updatepeerDependenciesso we must do it manually in our PRs when needed. See the updating peerDependencies section of the release instructions for more details.These changes have been verified by QA using a
?uiVersionthat includes a PR-Preview of this branch and thev_reqlabel has been applied to the issue.OD-UI E2E tests pass against these changes using a
?uiVersionthat includes a PR-Preview of this branch*CRITICAL
If you are making a breaking change, make sure to add the
BREAKING CHANGEcomment in the merge commit message. If this is not done,semantic-releasewill not do the right thing.If you find yourself in this position...
BREAKING CHANGEmessage in the merge commit.npm deprecate @esri/{package-name}@v{version-you-don't-want-out}