chore: release signage 0.1.3
0.1.3 ships the external package integration validated in #13 (Pass 2): the canonical linux-x64-glibc Module Package installed and exercised end to end by CI, with bounded external runtime image processing. Only the version moves: the manifest, package.json, the server runtime, both browser artifacts, the settings payload's moduleVersion, the test fixtures, and the README status line. compatibility stays platform ^0.2.0 and moduleSdk ^0.2.0; Core 0.2.4 already satisfies it, so the range is not tightened. pnpm-lock.yaml carries no root version and is unchanged. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
e83cdc62a7
commit
dd656eb18a
@@ -130,7 +130,7 @@ export function createSignageModuleRuntime(
|
||||
// Database ABI v1 executor, which `createSignageStore` binds Signage's own Drizzle adapter to.
|
||||
database: { abi: 1 },
|
||||
id: "signage",
|
||||
version: "0.1.2",
|
||||
version: "0.1.3",
|
||||
|
||||
register({ capabilities, config, http, realtime }) {
|
||||
const settings = readSignageSettings(config);
|
||||
@@ -192,7 +192,7 @@ export function createSignageModuleRuntime(
|
||||
// server enforces — a UI believing a stale limit would offer an upload the server refuses.
|
||||
return Response.json({
|
||||
crossfadeMs: current.crossfadeMs,
|
||||
moduleVersion: "0.1.2",
|
||||
moduleVersion: "0.1.3",
|
||||
nativeImageDurationMs: current.nativeImageDurationMs,
|
||||
nativePresentation: current.nativePresentation,
|
||||
rendererInputVersion: SIGNAGE_SLIDE_RENDERER_INPUT_VERSION,
|
||||
|
||||
Reference in New Issue
Block a user