chore(release): publish

[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 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

@ui5-community/jsx-runtime@0.1.3

Patch Changes

• #10 2e704f8 Thanks @petermuessig! - Fix: auto-prefix-id no longer prefixes UI5-generated ids (closes #9).

  Controls like sap.m.Menu create internal helper controls (e.g. a
  MenuWrapper) whose ids are generated by UI5 (matching
  ManagedObjectMetadata.isGeneratedId). Previously, when JSX constructed
  such controls inside a view with getAutoPrefixId() === true, those
  generated ids were passed through view.createId(), making the internal
  control unresolvable at add-time and causing a TypeError.

  The runtime now guards the createId() call with
  !ManagedObjectMetadata.isGeneratedId(rawId) so only author-supplied
  (static) ids are prefixed. Generated ids pass through untouched. Closes #9.

• #10 e9ffb68 Thanks @petermuessig! - JSX view-construction errors are now logged via sap/base/Log in addition
  to propagating. Previously, when createContent() threw (sync or async),
  the error was only visible as a rejected Promise and, in the showcase, as
  a text message rendered into the DOM. It was never written to the UI5 Log,
  making it invisible to log-scraping tooling and sap-ui-log-level debugging.

  installViewScopeBridge now wraps the createContent() call with a
  try/catch (sync) and a .catch on the returned Promise (async). On failure
  it calls Log.error with the full error message, the stack trace, and the
  component id "ui5.community.jsx.runtime", then re-throws / re-rejects so
  existing propagation behaviour is unchanged.

  The showcase's ExploreSample view also adds Log.error calls in both its
  demo-view and docs-load catch handlers so the exact user-facing message
  appears in the log as well.