Repository navigation
chore(release): version packages - #189
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 10, 2026 09:48
e4fd3db to
df800fb
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 publish to npm yourself or setup this action to publish 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
@cloudhal/[email protected]
Patch Changes
@cloudhal/[email protected]
Patch Changes
@cloudhal/[email protected]
Patch Changes
24fe76b: Security fixes from the CodeQL backlog on
main.updateDataModelpaths (@cloudhal/core-ts/interop) that name__proto__,constructororprototypeat any depth are now refused with anInteropErrorinstead of being skipped, step into arrays by index only, and write own properties only; an input whose component id is one of those keys gets the data key<id>-value. Surface pointers the page writes through (an input'svalue/checked, a Scrolly'sstep, a Button action'spath) may not name those keys (acheckSurfaceissue); read bindings still may. The Build eval's sample inputs never write through them, andset_chromeandupdate_entry'sfieldsmerge patch refuse them as keys.RESERVED_KEYSandisReservedKeyare new in@cloudhal/core-ts/names.htmlText(meta and feed descriptions, JSON-LD, table-of-contents labels) is plain text:<script>in markdown is the text<script>, as before, and every place it goes escapes it (now tested sink by sink). Tags are dropped with a linear scan, and entities are decoded once (&#60;is the text<, no longer<).<!--followed by many--><!--), the code-fence opener of surface bodies, the rich-text-to-text and text-to-rich-text field conversions, hostname normalization, the leading-H1 check of articles, the table of contents, the::embedcheck, the sender-address check (isMailAddress, new in@cloudhal/api;MAIL_ADDRESSin@cloudhal/cloudflare/mailis deprecated) and Studio's origin trim no longer backtrack. Each gives the old regex's answers; one intended difference: an svg comment ends at its first-->.Updated dependencies [24fe76b]
@cloudhal/[email protected]
Patch Changes
24fe76b: Security fixes from the CodeQL backlog on
main.updateDataModelpaths (@cloudhal/core-ts/interop) that name__proto__,constructororprototypeat any depth are now refused with anInteropErrorinstead of being skipped, step into arrays by index only, and write own properties only; an input whose component id is one of those keys gets the data key<id>-value. Surface pointers the page writes through (an input'svalue/checked, a Scrolly'sstep, a Button action'spath) may not name those keys (acheckSurfaceissue); read bindings still may. The Build eval's sample inputs never write through them, andset_chromeandupdate_entry'sfieldsmerge patch refuse them as keys.RESERVED_KEYSandisReservedKeyare new in@cloudhal/core-ts/names.htmlText(meta and feed descriptions, JSON-LD, table-of-contents labels) is plain text:<script>in markdown is the text<script>, as before, and every place it goes escapes it (now tested sink by sink). Tags are dropped with a linear scan, and entities are decoded once (&#60;is the text<, no longer<).<!--followed by many--><!--), the code-fence opener of surface bodies, the rich-text-to-text and text-to-rich-text field conversions, hostname normalization, the leading-H1 check of articles, the table of contents, the::embedcheck, the sender-address check (isMailAddress, new in@cloudhal/api;MAIL_ADDRESSin@cloudhal/cloudflare/mailis deprecated) and Studio's origin trim no longer backtrack. Each gives the old regex's answers; one intended difference: an svg comment ends at its first-->.Updated dependencies [24fe76b]
@cloudhal/[email protected]
Patch Changes
24fe76b: Security fixes from the CodeQL backlog on
main.updateDataModelpaths (@cloudhal/core-ts/interop) that name__proto__,constructororprototypeat any depth are now refused with anInteropErrorinstead of being skipped, step into arrays by index only, and write own properties only; an input whose component id is one of those keys gets the data key<id>-value. Surface pointers the page writes through (an input'svalue/checked, a Scrolly'sstep, a Button action'spath) may not name those keys (acheckSurfaceissue); read bindings still may. The Build eval's sample inputs never write through them, andset_chromeandupdate_entry'sfieldsmerge patch refuse them as keys.RESERVED_KEYSandisReservedKeyare new in@cloudhal/core-ts/names.htmlText(meta and feed descriptions, JSON-LD, table-of-contents labels) is plain text:<script>in markdown is the text<script>, as before, and every place it goes escapes it (now tested sink by sink). Tags are dropped with a linear scan, and entities are decoded once (&#60;is the text<, no longer<).<!--followed by many--><!--), the code-fence opener of surface bodies, the rich-text-to-text and text-to-rich-text field conversions, hostname normalization, the leading-H1 check of articles, the table of contents, the::embedcheck, the sender-address check (isMailAddress, new in@cloudhal/api;MAIL_ADDRESSin@cloudhal/cloudflare/mailis deprecated) and Studio's origin trim no longer backtrack. Each gives the old regex's answers; one intended difference: an svg comment ends at its first-->.Updated dependencies [24fe76b]
@cloudhal/[email protected]
Patch Changes
24fe76b: Security fixes from the CodeQL backlog on
main.updateDataModelpaths (@cloudhal/core-ts/interop) that name__proto__,constructororprototypeat any depth are now refused with anInteropErrorinstead of being skipped, step into arrays by index only, and write own properties only; an input whose component id is one of those keys gets the data key<id>-value. Surface pointers the page writes through (an input'svalue/checked, a Scrolly'sstep, a Button action'spath) may not name those keys (acheckSurfaceissue); read bindings still may. The Build eval's sample inputs never write through them, andset_chromeandupdate_entry'sfieldsmerge patch refuse them as keys.RESERVED_KEYSandisReservedKeyare new in@cloudhal/core-ts/names.htmlText(meta and feed descriptions, JSON-LD, table-of-contents labels) is plain text:<script>in markdown is the text<script>, as before, and every place it goes escapes it (now tested sink by sink). Tags are dropped with a linear scan, and entities are decoded once (&#60;is the text<, no longer<).<!--followed by many--><!--), the code-fence opener of surface bodies, the rich-text-to-text and text-to-rich-text field conversions, hostname normalization, the leading-H1 check of articles, the table of contents, the::embedcheck, the sender-address check (isMailAddress, new in@cloudhal/api;MAIL_ADDRESSin@cloudhal/cloudflare/mailis deprecated) and Studio's origin trim no longer backtrack. Each gives the old regex's answers; one intended difference: an svg comment ends at its first-->.Updated dependencies [24fe76b]
@cloudhal/[email protected]
Patch Changes
@cloudhal/[email protected]
Patch Changes
24fe76b: Security fixes from the CodeQL backlog on
main.updateDataModelpaths (@cloudhal/core-ts/interop) that name__proto__,constructororprototypeat any depth are now refused with anInteropErrorinstead of being skipped, step into arrays by index only, and write own properties only; an input whose component id is one of those keys gets the data key<id>-value. Surface pointers the page writes through (an input'svalue/checked, a Scrolly'sstep, a Button action'spath) may not name those keys (acheckSurfaceissue); read bindings still may. The Build eval's sample inputs never write through them, andset_chromeandupdate_entry'sfieldsmerge patch refuse them as keys.RESERVED_KEYSandisReservedKeyare new in@cloudhal/core-ts/names.htmlText(meta and feed descriptions, JSON-LD, table-of-contents labels) is plain text:<script>in markdown is the text<script>, as before, and every place it goes escapes it (now tested sink by sink). Tags are dropped with a linear scan, and entities are decoded once (&#60;is the text<, no longer<).<!--followed by many--><!--), the code-fence opener of surface bodies, the rich-text-to-text and text-to-rich-text field conversions, hostname normalization, the leading-H1 check of articles, the table of contents, the::embedcheck, the sender-address check (isMailAddress, new in@cloudhal/api;MAIL_ADDRESSin@cloudhal/cloudflare/mailis deprecated) and Studio's origin trim no longer backtrack. Each gives the old regex's answers; one intended difference: an svg comment ends at its first-->.@cloudhal/[email protected]
[email protected]
Patch Changes
@cloudhal/[email protected]
Patch Changes
24fe76b: Security fixes from the CodeQL backlog on
main.updateDataModelpaths (@cloudhal/core-ts/interop) that name__proto__,constructororprototypeat any depth are now refused with anInteropErrorinstead of being skipped, step into arrays by index only, and write own properties only; an input whose component id is one of those keys gets the data key<id>-value. Surface pointers the page writes through (an input'svalue/checked, a Scrolly'sstep, a Button action'spath) may not name those keys (acheckSurfaceissue); read bindings still may. The Build eval's sample inputs never write through them, andset_chromeandupdate_entry'sfieldsmerge patch refuse them as keys.RESERVED_KEYSandisReservedKeyare new in@cloudhal/core-ts/names.htmlText(meta and feed descriptions, JSON-LD, table-of-contents labels) is plain text:<script>in markdown is the text<script>, as before, and every place it goes escapes it (now tested sink by sink). Tags are dropped with a linear scan, and entities are decoded once (&#60;is the text<, no longer<).<!--followed by many--><!--), the code-fence opener of surface bodies, the rich-text-to-text and text-to-rich-text field conversions, hostname normalization, the leading-H1 check of articles, the table of contents, the::embedcheck, the sender-address check (isMailAddress, new in@cloudhal/api;MAIL_ADDRESSin@cloudhal/cloudflare/mailis deprecated) and Studio's origin trim no longer backtrack. Each gives the old regex's answers; one intended difference: an svg comment ends at its first-->.Updated dependencies [24fe76b]
@cloudhal/[email protected]
Patch Changes
@cloudhal/[email protected]
Patch Changes
@cloudhal/[email protected]
No changes in this release.