Skip to content

PU — EmuFramework v1.4.1

Latest

Choose a tag to compare

@emu479p01 emu479p01 released this 23 Oct 13:54
466bc7b

PU — EmuFramework v1.4.1

Summary

Update the framework runtime to Node.js 24.22.1 for the October 2026 security fixes and validate application and updater containers before publishing.

Fixes

  • Upgrade Node.js from 24.18.0 to 24.22.1 in development guidance, CI, release builds and both container images. Supported Node.js ranges now start at 22.23.4 and 24.22.1.
  • Replace the deprecated pnpm 11.12.0 release with 11.25.0 across the toolchain, retaining the existing dependency lockfile.
  • Upgrade workflow actions to versions declaring the Node.js 24 runtime and add repository version checks to CI.
  • Build both images before publishing either image. Validate their Node.js version, application SQLite native binding, startup health and restart health in CI and release workflows; publish the same validated images.

Breaking changes and migration

No application API, metadata or database schema changes. Source installations must update Node.js to a supported patched version before installing dependencies.

Upgrade notes

Back up the data and designer databases together. Upgrade both application and updater images to 1.4.1; replacing only the host Node.js does not update container runtimes. Source installations should use Node.js 24.22.1 and pnpm 11.25.0 and reinstall with the frozen lockfile. TLS validation is stricter upstream; integrations relying on non-canonical IP hostnames or revoked certificates may need corrected endpoints or certificates.

Validation

Validated locally on Node.js 24.22.1 and pnpm 11.25.0: frozen-lockfile installation, version consistency, PU release policy, type checking, production build, and 348 automated tests passed (one optional legacy-backup fixture skipped). Both Linux amd64 images built successfully; runtime version, SQLite native binding, startup and restart health checks passed. The existing persistent-database upgrade check passed from 1.3.0 to 1.4.1. Both GitHub workflows passed actionlint. GitHub CI is required before merge; this release has not been published.

Known issues

Registry publication of two images is not atomic: an upload failure can still leave only one versioned image published. Both images are built and checked before uploads begin, and latest tags are updated only after both versioned uploads succeed. Existing 1.4.0 application limitations still apply.