Release packages [publish docs] (alpha) - #1199
Closed
imodeljs-admin wants to merge 0 commit into
Closed
Conversation
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
January 28, 2026 07:45
b2aeef9 to
b9a2ff0
Compare
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
January 28, 2026 10:36
bfc1b87 to
d6174e0
Compare
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
January 28, 2026 11:18
69a0086 to
068834c
Compare
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
January 28, 2026 11:35
e7ab25b to
0b53819
Compare
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
January 29, 2026 08:59
f5358b3 to
60a1fb4
Compare
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
February 3, 2026 10:40
0da7a99 to
664acff
Compare
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
February 3, 2026 11:24
af21973 to
bc0cc22
Compare
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
February 4, 2026 09:39
4ae2f6f to
23add2d
Compare
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
February 4, 2026 11:24
ede9048 to
820f14d
Compare
imodeljs-admin
force-pushed
the
changeset-release/next
branch
from
February 4, 2026 11:35
c9c1de3 to
7e7241f
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 next, this PR will be updated.
nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonnext.Releases
@itwin/presentation-hierarchies@2.0.0-alpha.11
Major Changes
#1198: Change
HierarchyProvider.hierarchyChangedargument to be required.This simplifies the API for users of
HierarchyProvider, as they no longer need to check forundefinedwhen handling hierarchy changes.For implementors of custom
HierarchyProvider, this change means that they must always provide an even argument when raising thehierarchyChangedevent. Since all members of the argument type are optional, it's okay to raise the even with an empty object, e.g.:this.hierarchyChanged.raiseEvent({}).#1202: Change
NodePreProcessorandNodePostProcessorfunction types to take a props object instead of a node.In addition, the props object now contains the
parentNodeproperty, which provides access to the parent node of the current node being processed. This allows for more context-aware processing of nodes within the hierarchy.The change breaks consumers that have
HierarchyDefinitionimplementations withpreProcessNodeorpostProcessNodefunctions defined. Reacting to the change is straightforward:Minor Changes
#1204: Add
createHierarchyProviderutility function.This function simplifies the creation of custom hierarchy providers by allowing developers to define only the necessary methods, while providing default implementations for the rest. This enhancement improves developer experience and reduces boilerplate code when working with custom hierarchy providers in the
@itwin/presentation-hierarchiespackage.Before:
After:
Patch Changes
@itwin/presentation-shared@2.0.0-alpha.7
Major Changes
EC.RelationshipConstraint.multiplicityrequired.Minor Changes
RaisableEventinterface, which extendsEventwith additionalraiseEventmethod.Patch Changes
#1198: Fix
Eventtype to prohibit being assigned an event with no-argument listener (unless the target event uses a no-argument listener).Now TS will complain about the following assignment, which it previously allowed:
@itwin/presentation-core-interop@1.4.0-alpha.6
Patch Changes
@itwin/presentation-hierarchies-react@2.0.0-alpha.54
Patch Changes
#1198: Change
HierarchyProvider.hierarchyChangedargument to be required.This simplifies the API for users of
HierarchyProvider, as they no longer need to check forundefinedwhen handling hierarchy changes.For implementors of custom
HierarchyProvider, this change means that they must always provide an even argument when raising thehierarchyChangedevent. Since all members of the argument type are optional, it's okay to raise the even with an empty object, e.g.:this.hierarchyChanged.raiseEvent({}).#1200: Removed unnecessary, always-truthy condition checks.
#1193: Process package output with React Compiler.
Updated dependencies: