Skip to main content

Upgrading To New Versions

hosanna.json is the checked-in source-distribution and compiler contract for an application. Upgrade it intentionally on a reviewable branch; do not let a developer's global tools or local SDK checkout choose production versions.

Example hosanna.json:

{
  "distribution": "keygen",
  "sdk-version": "v1.30.2",
  "transpiler-version": "1.43.2",
  "flavour": "fullSource"
}
  • distribution: licensed release source, normally keygen for current full-source applications.
  • sdk-version: exact framework publication selected for production.
  • transpiler-version: exact Hosanna Compiler release.
  • flavour: entitled SDK source flavour.

The numbers above illustrate the current sample toolchain; copy the structure, not a stale version.

Keeping Your Project Up To Date​

  1. Confirm the active license and current install:

    npx hst license:status
    npx hst config source
    npx hst compiler:status

  2. Update the exact sdk-version and transpiler-version in hosanna.json. Review the framework/compiler release notes and migration requirements.

  3. Restore the declared versions:

    npx hst framework:update
    npx hst compiler:install

    framework:update is a no-op when the Keygen-installed SDK is already at the declared version. It refuses unsafe replacement of modified source.

  4. Regenerate and run the application validation matrix:

    npm run generate
    npm run lint
    npm run build
    npm test
    npm run roku:build:dev
    npm run roku:build:prod

  5. Build the native targets included by the application:

npx hst build ios dev sim --device "iPhone 17 Pro" --non-interactive
npx hst build apple-tv dev sim --device "Apple TV 4K" --non-interactive
npx hst build android dev sim --device Pixel_8 --non-interactive
npx hst build android-tv dev sim --device Television_1080p --non-interactive

Use only the scripts and targets that exist in the application. Qualifying latest can help evaluate a publication, but return production to an exact pin before merging or releasing.

Commit hosanna.json and any deliberate application migrations together. Do not commit the downloaded hosanna-ui/ directory, a local embedded/shared source path, generated files, or license material.

See Licensed SDK Source Distribution for source modes, integrity checks, and CI handling.

Talk to us