Skip to content

Core

Independent SDK adoption and App compatibility

0.5.0

Adopt the independent Laravel and React SDK packages, update App compatibility for Core 0.5.0, and improve local development, reports, onboarding, and navigation.

Changed

  • Core adopts the independent App SDK artifacts: PHP amuzcorp/nexia-app-sdk-laravel 0.5.0 and React @amuzcorp/nexia-app-sdk-react 0.5.0. The former combined SDK package and its legacy namespaces are no longer supported by Core.
  • The published Apps retain independent versions and already require the two SDK artifacts at ^0.5.0. Before adopting Core 0.5.0, publish App releases whose extra.nexia.core_version declares ^0.5.0, then regenerate the Composer and pnpm locks from those released artifacts.
  • Local setup and rebuild prepare missing application keys before Composer boots Laravel, and restore private Composer and npm authentication from ignored auth.json or an approved host credential fallback. Rotate a local PAT with task apps:auth REPLACE=1.
  • When a local React SDK source is selected, Vite starts its SDK build watcher before the Core dev server. SDK source edits re-emit the linked distribution without reinstalling dependencies, including when the development lock is in .pnpm-local.
  • Report authors can configure base and connected data, result layout, filters, calculations, and sorting together. Demo report seeding adds business-data examples without replacing user-edited definitions.
  • Onboarding can resume a user-private assistant conversation and supports either organization-chart import or direct operating-unit setup. Existing ordinary Agent conversations are not reclassified automatically.
  • Ordinary navigation keeps the current work tab. Supported links can explicitly open a new internal work tab, while pane relocation, merging, and destructive close actions require clear user choices.

Fixed

  • Refreshing local packages clears the prior contribution manifest only before a real Composer package change, avoiding stale installed-package metadata.
  • Organization import review prevents descendant-parent selections and repeated mapping columns, clears stale previews and corrections when source data changes, and keeps edit actions unavailable while validation is running.
  • Saved dashboard rows retain their Favorite and Set as default actions in the context menu when opened as navigation links.
  • Onboarding progress task rows use the standard button control, keeping focus and disabled behavior consistent.

Upgrade required

  • Run the tenant migration that adds the nullable Agent conversation purpose and one private onboarding conversation per user. Earlier ordinary conversations are retained and are not converted automatically.
  • The bundled Payroll 0.3.3 tenant migration corrects existing standard tax and insurance element categories. Run normal tenant migrations during the upgrade; no separate data-repair step is required. Its down migration intentionally does not reverse this correction, so already-correct tenant rows are not changed.
  • Do not combine the retired SDK package with either 0.5.0 SDK artifact. Use the released SDK artifacts and App releases compatible with Core ^0.5.0 to regenerate and commit the Composer and pnpm locks before deployment.