Documentation / Ship & maintain
Updating a product
Creator Core separates shared behavior from editable visual source and application services. Choose the update path matching the change. A runtime package update does not deploy a backend or rewrite your product.
Update the shared runtime
Review the published release notes, then accept the dependency update or install the intended exact version:
bun add @nintu/creator-core-runtime@0.2.7
bun run check
bun run build:cloudflare
Commit package.json and bun.lock together. Verify the affected interactions, then deploy your product through its own workflow. The initialized starter includes a Dependabot configuration for public runtime updates; it needs no private package-read token.
Update editable components
Compare the selected bundle with your customized source:
bunx --bun shadcn add itsNintu/creator-core-kit/motion-primitives#v0.2.7 --diff
Merge the changes you want. Keep your product's styles and behavior, and update the related preview at the same time. Do not use --overwrite as an unattended update strategy. The component catalog and registry refer to the same maintained implementations, but your installed visual source belongs to your product.
Update scaffolding and backend behavior
Follow the release's migration instructions for routes, account operations, Convex functions/schema, configuration, and workflows. These are local product changes. Coordinate frontend changes with backend sync and live service verification.
Do not merge the complete upstream application as your routine upgrade mechanism. New template copies have independent histories, and automatic runtime updates preserve customized source.
Move from the private package to public npm
The public package is @nintu/creator-core-runtime; the older private package is @itsnintu/creator-core-runtime. Replace the dependency rather than installing both:
bun remove @itsnintu/creator-core-runtime
bun add @nintu/creator-core-runtime@0.2.7
Replace the @itsnintu/creator-core-runtime prefix with @nintu/creator-core-runtime in TypeScript imports, compatibility re-exports, and the CSS stylesheet import. The exported subpaths and runtime behavior are unchanged. For example, the stylesheet becomes @import "@nintu/creator-core-runtime/styles.css"; and the motion entry becomes @nintu/creator-core-runtime/motion.
The new package comes from https://registry.npmjs.org. Remove the old @itsnintu GitHub Packages scope configuration only if no other dependency still uses it. Keep any unrelated registry routes and credentials. Commit the resulting package.json, bun.lock, source imports, and configuration changes together.
Remove Creator Core's obsolete package-authentication setup from that product's Actions and Dependabot configuration. Preserve credentials used by other dependencies or services. Public npm installs need no Creator Core read token.
Review the public release's source migrations separately. Replacing the package does not copy a new homepage, account implementation, or database policy into your product. Do not rerun init:product on an existing customized application.
Verify the complete change
Run product checks and the Worker build, then verify the changed UI or signed-in flow against the intended services. For account or data changes, test the relevant permission boundaries and empty/error states. Review the staged diff before committing so unrelated work and secrets stay out of the update.