[github-actions]

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

@bedrock-core/catalog@0.2.0

Minor Changes

• ae304d5 Thanks @drav0011! - Export CATALOG_PAGE_AREA from the Catalog and its integration entry point so custom addon pages share the host geometry.

• 529eaf0 Thanks @drav0011! - Register application entry points through navigation(core), reconstruct private models in their owning realm and preserve destination inputs across realm transitions. Determine catalog button availability from registered screens. Export manifest-page publishing separately through @bedrock-core/catalog/integration.

Patch Changes

• 8ca3ae0 Thanks @drav0011! - Select the catalog's own addon when its entry point opens without an explicit selection.

• 81e64d9 Thanks @drav0011! - Require the released navigation and UI libraries and the stable reactive packages.

• 529eaf0 Thanks @drav0011! - Use resident client navigation for the catalog's framework guide.

• Updated dependencies [6ba1736, ae304d5, 529eaf0, 529eaf0, 529eaf0, 529eaf0, 54683fa, 81e64d9, 529eaf0, 529eaf0]:

  • @bedrock-core/guides@0.3.0

@bedrock-core/config@0.4.0

Minor Changes

• 6ba1736 Thanks @drav0011! - Use a bounded client navigation stack for schema menus, enable resets only for non-default values, and preserve invalid editor submissions with localized field errors. Recheck permissions before applying resets and edits. Compile schema menu pages at their authored row capacities.

  Use consistent card bounds and menu row spacing across scope selection and schema pages. Preserve list-setting breadcrumbs and their parent destinations.

• 529eaf0 Thanks @drav0011! - Register application entry points through navigation(core), reconstruct private models in their owning realm and preserve destination inputs across realm transitions. Determine catalog button availability from registered screens. Export manifest-page publishing separately through @bedrock-core/catalog/integration.

Patch Changes

• 27ce262 Thanks @drav0011! - Lay out number sliders below their captions and descriptions so the native track keeps their text readable.

• 529eaf0 Thanks @drav0011! - Use the navigation host extension entry point and the renderer's shared screen metadata contracts.

• 54683fa Thanks @drav0011! - Keep Config and Guides internal navigation routes independent of the consumer's registered root navigator types.

• 8b77121 Thanks @drav0011! - Keep schema menu navigation on the client with loop-collapsing history and full section ancestry.

• 81e64d9 Thanks @drav0011! - Require the released navigation and UI libraries and the stable reactive packages.

@bedrock-core/guides@0.3.0

Minor Changes

• 529eaf0 Thanks @drav0011! - Render Guides through the shared static stack with bounded local transitions, visited-page Back history and complete server checkpoints. Custom MDX components use the navigation package Links and hooks.

• 529eaf0 Thanks @drav0011! - Provide audience-filtered static guide screens with local page selection and navigation checkpoints for MDX actions. Restore confirmed navigator state across server actions and caller handoffs.

• 529eaf0 Thanks @drav0011! - Register application entry points through navigation(core), reconstruct private models in their owning realm and preserve destination inputs across realm transitions. Determine catalog button availability from registered screens. Export manifest-page publishing separately through @bedrock-core/catalog/integration.

Patch Changes

• 6ba1736 Thanks @drav0011! - Render guide index entries as text links with optional icons and descriptions, preserving category nesting and local navigation history.

• ae304d5 Thanks @drav0011! - Keep guide reading client-side with sibling pagination, loop removal, and five retained Back destinations. Require complete native history coverage at build time.

• 529eaf0 Thanks @drav0011! - Hide the Index action on hidden guide pages while retaining it on declared home and category landing pages. Keep its square button inside the footer at the same size with or without pagination controls.

• 529eaf0 Thanks @drav0011! - Use the navigation host extension entry point and the renderer's shared screen metadata contracts.

• 54683fa Thanks @drav0011! - Keep Config and Guides internal navigation routes independent of the consumer's registered root navigator types.

• 81e64d9 Thanks @drav0011! - Require the released navigation and UI libraries and the stable reactive packages.

• 529eaf0 Thanks @drav0011! - Preserve Ore layout dimensions and intrinsic captions in resident guide navigation controls. Keep the Index control aligned on eligible pages with or without pagination neighbors.