📦 Publish SDKs

[builder-io-integration]

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

@builder.io/sdk@6.3.2

Patch Changes

• d9afb88: Types: add optional group?: string to the component metadata type used by Builder.registerComponent, so TypeScript integrations can bucket custom components into their own accordions in the editor's insert menu without excess-property errors.

@builder.io/react@9.4.3

Patch Changes

• Updated dependencies [d9afb88]
  • @builder.io/sdk@6.3.2

@builder.io/sdk-angular@0.25.10

Patch Changes

• d9afb88: Types: add optional group?: string to the component metadata type used by Builder.registerComponent, so TypeScript integrations can bucket custom components into their own accordions in the editor's insert menu without excess-property errors.

@builder.io/sdk-react-nextjs@0.25.10

Patch Changes

• d9afb88: Types: add optional group?: string to the component metadata type used by Builder.registerComponent, so TypeScript integrations can bucket custom components into their own accordions in the editor's insert menu without excess-property errors.

@builder.io/sdk-qwik@0.25.10

Patch Changes

• d9afb88: Types: add optional group?: string to the component metadata type used by Builder.registerComponent, so TypeScript integrations can bucket custom components into their own accordions in the editor's insert menu without excess-property errors.

@builder.io/sdk-react@5.2.8

Patch Changes

• d9afb88: Types: add optional group?: string to the component metadata type used by Builder.registerComponent, so TypeScript integrations can bucket custom components into their own accordions in the editor's insert menu without excess-property errors.

@builder.io/sdk-react-native@5.2.8

Patch Changes

• d9afb88: Types: add optional group?: string to the component metadata type used by Builder.registerComponent, so TypeScript integrations can bucket custom components into their own accordions in the editor's insert menu without excess-property errors.

@builder.io/sdk-solid@5.2.8

Patch Changes

• d9afb88: Types: add optional group?: string to the component metadata type used by Builder.registerComponent, so TypeScript integrations can bucket custom components into their own accordions in the editor's insert menu without excess-property errors.

@builder.io/sdk-svelte@5.2.8

Patch Changes

• d9afb88: Types: add optional group?: string to the component metadata type used by Builder.registerComponent, so TypeScript integrations can bucket custom components into their own accordions in the editor's insert menu without excess-property errors.

@builder.io/sdk-vue@5.2.8

Patch Changes

• d9afb88: Types: add optional group?: string to the component metadata type used by Builder.registerComponent, so TypeScript integrations can bucket custom components into their own accordions in the editor's insert menu without excess-property errors.

[nx-cloud]

🤖 Nx Cloud AI Fix Eligible

An automatically generated fix could have helped fix failing tasks for this run, but Self-healing CI is disabled for this workspace. Visit workspace settings to enable it and get automatic fixes in future runs.

_{To disable these notifications, a workspace admin can disable them in workspace settings.}

---

View your CI Pipeline Execution ↗ for commit a690780

Command	Status	Duration	Result
nx test @e2e/react-native-74	❌ Failed	3m 38s	View ↗
nx test @e2e/nextjs-sdk-next-app	✅ Succeeded	7m 5s	View ↗
nx test @e2e/qwik-city	✅ Succeeded	7m 19s	View ↗
nx test @e2e/gen1-remix	✅ Succeeded	4m 50s	View ↗
nx test @e2e/angular-17	✅ Succeeded	6m 37s	View ↗
nx test @e2e/angular-17-ssr	✅ Succeeded	5m 20s	View ↗
nx test @e2e/sveltekit	✅ Succeeded	4m 38s	View ↗
nx test @e2e/gen1-next14-pages	✅ Succeeded	4m 5s	View ↗
Additional runs (38)	✅ Succeeded	...	View ↗

💡 Dealing with memory or CPU issues? See memory and CPU details with the resource usage add-on ↗.

---

☁️ Nx Cloud last updated this comment at 2026-08-18 12:25:43 UTC

[builder-io-integration]

Builder reviewed your changes — looks good ✅

Review Details

Incremental Code Review Summary

I reviewed the latest head of PR #4795 following the prior clean incremental reviews. The PR is still a Changesets-generated release-only update: it bumps package versions, adds corresponding changelog entries, records the @builder.io/react dependency release for @builder.io/sdk@6.3.2, and removes the consumed changeset. No runtime source or UI files are changed.

This remains low risk. All nine SDK packages listed by the changeset are version-bumped, all ten changed package manifests match their changelog headings, linked package groups remain consistent, and the generated release metadata has no dependency, package-boundary, or publishing errors. Both independent agents found no genuinely new issues, and there are no previous findings to resolve or resubmit.

Key Findings

• No new high- or medium-severity issues found.
• ✅ Package versions and changelogs match.
• ✅ Changeset coverage and deletion are correct.
• ✅ Linked-package and dependency release metadata is consistent.

🧪 Browser testing: Skipped — PR only modifies release metadata and changelogs, with no UI impact.