Skip to content

chore: Bump the cloudhal group with 12 updates - #24

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/npm_and_yarn/cloudhal-2028fb378d
Oct 26, 2026
Merged

chore: Bump the cloudhal group with 12 updates#24
github-actions[bot] merged 1 commit into
mainfrom
dependabot/npm_and_yarn/cloudhal-2028fb378d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 26, 2026

Copy link
Copy Markdown
Contributor

Bumps the cloudhal group with 12 updates:

Package From To
@cloudhal/astro-renderer 0.6.0 0.6.1
@cloudhal/cli 0.6.0 0.6.1
@cloudhal/core-ts 0.6.0 0.6.1
@cloudhal/cloudflare 0.6.0 0.6.1
@cloudhal/agent-runtime 0.6.0 0.6.1
@cloudhal/analytics 0.6.0 0.6.1
@cloudhal/api 0.6.0 0.6.1
@cloudhal/comments 0.6.0 0.6.1
@cloudhal/core-contracts 0.6.0 0.6.1
@cloudhal/mcp-server 0.6.0 0.6.1
@cloudhal/schedules 0.6.0 0.6.1
@cloudhal/storage 0.6.0 0.6.1

Updates @cloudhal/astro-renderer from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/astro-renderer's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

Upgrade

npm install @cloudhal/cli@0.6.1 @cloudhal/core-ts@0.6.1 @cloudhal/astro-renderer@0.6.1 @cloudhal/cloudflare@0.6.1
npx cloudhal deploy

Docs: https://cloudhal.dev/docs/start/installation#upgrading

Changelog

Sourced from @​cloudhal/astro-renderer's changelog.

0.6.1

Patch Changes

  • 92c3867: Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Updated dependencies [40dbfcb]

  • Updated dependencies [028f396]

    • @​cloudhal/core-ts@​0.6.1
    • @​cloudhal/comments@​0.6.1
    • @​cloudhal/analytics@​0.6.1
    • @​cloudhal/core-contracts@​0.6.1
    • @​cloudhal/storage@​0.6.1
Commits
  • ba05c90 chore(release): version packages
  • 92c3867 fix(renderer): ship theme scripts as files; render_page names broken surfaces...
  • See full diff in compare view

Updates @cloudhal/cli from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/cli's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

Upgrade

npm install @cloudhal/cli@0.6.1 @cloudhal/core-ts@0.6.1 @cloudhal/astro-renderer@0.6.1 @cloudhal/cloudflare@0.6.1
npx cloudhal deploy

Docs: https://cloudhal.dev/docs/start/installation#upgrading

Changelog

Sourced from @​cloudhal/cli's changelog.

0.6.1

Patch Changes

  • 40dbfcb: Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • 4103a32: Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

  • 92c3867: Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Updated dependencies [40dbfcb]

  • Updated dependencies [028f396]

  • Updated dependencies [92c3867]

    • @​cloudhal/core-ts@​0.6.1
    • @​cloudhal/mcp-server@​0.6.1
    • @​cloudhal/api@​0.6.1
    • @​cloudhal/cloudflare@​0.6.1
    • @​cloudhal/comments@​0.6.1
    • @​cloudhal/agent-runtime@​0.6.1
    • @​cloudhal/analytics@​0.6.1
    • @​cloudhal/core-contracts@​0.6.1
    • @​cloudhal/schedules@​0.6.1
    • @​cloudhal/storage@​0.6.1
Commits
  • ba05c90 chore(release): version packages
  • 96a904f Merge pull request #120 from cloudhal-dev/fix/theme-scripts-csp
  • 40dbfcb fix: section-only blocks in bodies, list_entries default, long-line per colum...
  • 92c3867 fix(renderer): ship theme scripts as files; render_page names broken surfaces...
  • See full diff in compare view

Updates @cloudhal/core-ts from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/core-ts's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

Upgrade

npm install @cloudhal/cli@0.6.1 @cloudhal/core-ts@0.6.1 @cloudhal/astro-renderer@0.6.1 @cloudhal/cloudflare@0.6.1
npx cloudhal deploy

Docs: https://cloudhal.dev/docs/start/installation#upgrading

Changelog

Sourced from @​cloudhal/core-ts's changelog.

0.6.1

Patch Changes

  • 40dbfcb: Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • 028f396: A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • @​cloudhal/core-contracts@​0.6.1

    • @​cloudhal/schedules@​0.6.1
    • @​cloudhal/storage@​0.6.1
Commits
  • ba05c90 chore(release): version packages
  • 36536c8 Merge pull request #121 from cloudhal-dev/fix/body-blocks-and-tools
  • 028f396 fix(core-ts): allow the collection index page at a permalink prefix
  • 40dbfcb fix: section-only blocks in bodies, list_entries default, long-line per colum...
  • See full diff in compare view

Updates @cloudhal/cloudflare from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/cloudflare's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

Upgrade

npm install @cloudhal/cli@0.6.1 @cloudhal/core-ts@0.6.1 @cloudhal/astro-renderer@0.6.1 @cloudhal/cloudflare@0.6.1
npx cloudhal deploy

Docs: https://cloudhal.dev/docs/start/installation#upgrading

Changelog

Sourced from @​cloudhal/cloudflare's changelog.

0.6.1

Patch Changes

  • Updated dependencies [40dbfcb]
  • Updated dependencies [028f396]
  • Updated dependencies [92c3867]
    • @​cloudhal/core-ts@​0.6.1
    • @​cloudhal/mcp-server@​0.6.1
    • @​cloudhal/api@​0.6.1
    • @​cloudhal/comments@​0.6.1
    • @​cloudhal/agent-runtime@​0.6.1
    • @​cloudhal/analytics@​0.6.1
    • @​cloudhal/schedules@​0.6.1
    • @​cloudhal/storage@​0.6.1
Commits

Updates @cloudhal/agent-runtime from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/agent-runtime's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

Upgrade

npm install @cloudhal/cli@0.6.1 @cloudhal/core-ts@0.6.1 @cloudhal/astro-renderer@0.6.1 @cloudhal/cloudflare@0.6.1
npx cloudhal deploy

Docs: https://cloudhal.dev/docs/start/installation#upgrading

Changelog

Sourced from @​cloudhal/agent-runtime's changelog.

0.6.1

Patch Changes

  • @​cloudhal/core-contracts@​0.6.1
    • @​cloudhal/storage@​0.6.1
Commits

Updates @cloudhal/analytics from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/analytics's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

Upgrade

npm install @cloudhal/cli@0.6.1 @cloudhal/core-ts@0.6.1 @cloudhal/astro-renderer@0.6.1 @cloudhal/cloudflare@0.6.1
npx cloudhal deploy

Docs: https://cloudhal.dev/docs/start/installation#upgrading

Changelog

Sourced from @​cloudhal/analytics's changelog.

0.6.1

Patch Changes

  • @​cloudhal/core-contracts@​0.6.1
    • @​cloudhal/storage@​0.6.1
Commits

Updates @cloudhal/api from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/api's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

Upgrade

npm install @cloudhal/cli@0.6.1 @cloudhal/core-ts@0.6.1 @cloudhal/astro-renderer@0.6.1 @cloudhal/cloudflare@0.6.1
npx cloudhal deploy

Docs: https://cloudhal.dev/docs/start/installation#upgrading

Changelog

Sourced from @​cloudhal/api's changelog.

0.6.1

Patch Changes

  • Updated dependencies [40dbfcb]
  • Updated dependencies [028f396]
  • Updated dependencies [92c3867]
    • @​cloudhal/core-ts@​0.6.1
    • @​cloudhal/mcp-server@​0.6.1
    • @​cloudhal/astro-renderer@​0.6.1
    • @​cloudhal/comments@​0.6.1
    • @​cloudhal/agent-runtime@​0.6.1
    • @​cloudhal/analytics@​0.6.1
    • @​cloudhal/core-contracts@​0.6.1
    • @​cloudhal/schedules@​0.6.1
    • @​cloudhal/storage@​0.6.1
Commits
  • ba05c90 chore(release): version packages
  • 028f396 fix(core-ts): allow the collection index page at a permalink prefix
  • See full diff in compare view

Updates @cloudhal/comments from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/comments's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

Upgrade

npm install @cloudhal/cli@0.6.1 @cloudhal/core-ts@0.6.1 @cloudhal/astro-renderer@0.6.1 @cloudhal/cloudflare@0.6.1
npx cloudhal deploy

Docs: https://cloudhal.dev/docs/start/installation#upgrading

Changelog

Sourced from @​cloudhal/comments's changelog.

0.6.1

Patch Changes

  • Updated dependencies [40dbfcb]
  • Updated dependencies [028f396]
    • @​cloudhal/core-ts@​0.6.1
    • @​cloudhal/core-contracts@​0.6.1
    • @​cloudhal/storage@​0.6.1
Commits

Updates @cloudhal/core-contracts from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/core-contracts's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script> (under 4 KB) into the page, where the Site Worker's script-src 'self' blocked it: script chunks always ship as files (build.assetsInlineLimit), other assets keep the project's own limit. A theme that set vite.build.assetsInlineLimit itself for this can drop it.
    • cloudhal dev sends the Site Worker's policy as Content-Security-Policy-Report-Only on pages without their own, so the browser console shows what a deploy would block without breaking Vite's dev client.
    • render_page and cloudhal render gain two checks: surface-broken (a body ```surface fence the preview cannot draw, or a component with an unknown block type or props that do not fit, named with the problem) and script-blocked (a script the page's CSP refused, inline or by URL; under cloudhal dev's report-only policy, what a deploy would block).

  • Studio on a playground (RFC-0036): the Build page no longer says "This deployment can't reach Workers AI". It says Build with AI is available in your own install, since the playground leaves AI out, and links to deploying Cloudhal. Translations of the new sentence are AI drafts awaiting review.

Upgrade

npm install @cloudhal/cli@0.6.1 @cloudhal/core-ts@0.6.1 @cloudhal/astro-renderer@0.6.1 @cloudhal/cloudflare@0.6.1
npx cloudhal deploy

Docs: https://cloudhal.dev/docs/start/installation#upgrading

Changelog

Sourced from @​cloudhal/core-contracts's changelog.

0.6.1

No changes in this release.

Commits

Updates @cloudhal/mcp-server from 0.6.0 to 0.6.1

Release notes

Sourced from @​cloudhal/mcp-server's releases.

Cloudhal 0.6.1

All @cloudhal/* packages and create-cloudhal at 0.6.1.

Changes

  • Gaps an agent hit building a site through MCP:

    • Section-only theme blocks in article bodies are refused. A theme block type with where: ["section"] (say link-cards) has no component in an article, and drew "unknown component" there. create_entry/update_entry now refuse it inside a body ```surface fence (invalid_surface, with the component's path); primitives, built-in blocks and theme blocks that allow body stay. get_catalog's "In article bodies" lists which blocks a body may use and which are page sections only.
    • list_entries lists every collection by default, not only posts: a site whose articles live in blog got []. where/orderBy need the collection whose list fields they use; without one they are refused (invalid_query at collection) instead of ignored.
    • long-line gives a text column one verdict. It counted characters over a rounded line count, so how full a paragraph's last line was decided whether it passed, and identical paragraphs in one column disagreed. It now counts the characters on each rendered line, leaves each paragraph's last line out, and pools the paragraphs of one width and font: one example per column, with its width and how many paragraphs it holds.
    • Blog starter: a primary surface Button in an article body keeps its on-brand text; the body's link colour no longer applies to buttons (it failed contrast at 2.5:1 light, 1.3:1 dark).

  • A collection's template may now sit on top of a page at its prefix: set_collection_permalink with posts → /blog/{slug} no longer fails with path_conflict because a page lives at /blog. That page is the collection's index page (RFC-0038), so only pages strictly under the prefix conflict, in the template check, its SQL race guard (noPageUnder) and the reverse check on page writes. Studio's "Create listing page" now works for a collection with its own permalink too.

  • Theme scripts work on deployed sites, and render_page says when they would not.

    • The cloudhal() integration no longer lets Astro inline a component's <script>Description has been truncated

@dependabot
chore: Bump the cloudhal group with 12 updates
7d0e6c7 
Bumps the cloudhal group with 12 updates:

| Package | From | To |
| --- | --- | --- |
| [@cloudhal/astro-renderer](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/astro-renderer) | `0.6.0` | `0.6.1` |
| [@cloudhal/cli](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/cli) | `0.6.0` | `0.6.1` |
| [@cloudhal/core-ts](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/core-ts) | `0.6.0` | `0.6.1` |
| [@cloudhal/cloudflare](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/cloudflare) | `0.6.0` | `0.6.1` |
| [@cloudhal/agent-runtime](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/agent-runtime) | `0.6.0` | `0.6.1` |
| [@cloudhal/analytics](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/analytics) | `0.6.0` | `0.6.1` |
| [@cloudhal/api](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/api) | `0.6.0` | `0.6.1` |
| [@cloudhal/comments](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/comments) | `0.6.0` | `0.6.1` |
| [@cloudhal/core-contracts](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/core-contracts) | `0.6.0` | `0.6.1` |
| [@cloudhal/mcp-server](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/mcp-server) | `0.6.0` | `0.6.1` |
| [@cloudhal/schedules](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/schedules) | `0.6.0` | `0.6.1` |
| [@cloudhal/storage](https://github.com/cloudhal-dev/cloudhal/tree/HEAD/packages/storage) | `0.6.0` | `0.6.1` |


Updates `@cloudhal/astro-renderer` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/astro-renderer/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/astro-renderer)

Updates `@cloudhal/cli` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/cli)

Updates `@cloudhal/core-ts` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/core-ts/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/core-ts)

Updates `@cloudhal/cloudflare` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/cloudflare/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/cloudflare)

Updates `@cloudhal/agent-runtime` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/agent-runtime/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/agent-runtime)

Updates `@cloudhal/analytics` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/analytics/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/analytics)

Updates `@cloudhal/api` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/api/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/api)

Updates `@cloudhal/comments` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/comments/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/comments)

Updates `@cloudhal/core-contracts` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/core-contracts/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/core-contracts)

Updates `@cloudhal/mcp-server` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/mcp-server/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/mcp-server)

Updates `@cloudhal/schedules` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/schedules/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/schedules)

Updates `@cloudhal/storage` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/cloudhal-dev/cloudhal/releases)
- [Changelog](https://github.com/cloudhal-dev/cloudhal/blob/main/packages/storage/CHANGELOG.md)
- [Commits](https://github.com/cloudhal-dev/cloudhal/commits/v0.6.1/packages/storage)

---
updated-dependencies:
- dependency-name: "@cloudhal/astro-renderer"
  dependency-version: 0.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/cli"
  dependency-version: 0.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/core-ts"
  dependency-version: 0.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/cloudflare"
  dependency-version: 0.6.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/agent-runtime"
  dependency-version: 0.6.1
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/analytics"
  dependency-version: 0.6.1
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/api"
  dependency-version: 0.6.1
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/comments"
  dependency-version: 0.6.1
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/core-contracts"
  dependency-version: 0.6.1
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/mcp-server"
  dependency-version: 0.6.1
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/schedules"
  dependency-version: 0.6.1
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: cloudhal
- dependency-name: "@cloudhal/storage"
  dependency-version: 0.6.1
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: cloudhal
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 26, 2026
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 26, 2026 •
edited
Loading

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs		 cloudhal-com-site 7d0e6c7 Oct 26 2026, 03:18 AM

@github-actions
github-actions Bot merged commit 7df817a into main Oct 26, 2026
3 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/cloudhal-2028fb378d branch October 26, 2026 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants