Past releases

These are the records of earlier Lolly and Work releases: what each paired, what it changed, its migrations and its image digests. For the current release, read Release 1.1.2. Each release's own tagged documentation stays on GitHub, linked from its section.

1.1.1

Work 1.1.1 paired the Work server and render worker with Lolly 1.1.1, built from Lolly source 26cf05324f46dc4cacd65d12d6f454ada181fb5e, and is published as Work v1.1.1. Its tagged installation guide, deployment options and documentation index describe it as released.

The engine version did not change from Work 1.1.0's final pin, but its content did: the Lolly source moved from 3b0edf3d6 to 26cf05324, so the packed content hashes changed. Audiogram 2.7.5, Captions 1.0.4 and Record 1.4.3 need engine 1.261.0 or later wherever they render, including the Work server.

What 1.1.1 changed

• Tool scripts and styles load from blob: addresses. The web app turns verified tool scripts and styles into blob: addresses, and its script-src and style-src now allow blob:, both in server/src/api/shell-headers.ts and in the YunoHost deploy/yunohost/conf/shell-headers.inc. Before this change the policy refused those loads, so tools whose libraries load this way, such as 3D, fell back to reduced output.
• The render worker serves HTTPS. Set LW_RENDER_TLS_CERT_FILE and LW_RENDER_TLS_KEY_FILE, with optional LW_RENDER_TLS_CA_FILE and LW_RENDER_TLS_SERVER_NAME. The chart takes renderWorker.tls.existingSecret, serverName and caSecret, and generates no private key. The published 1.1.0 worker image serves plain HTTP, so it fails this chart's HTTPS probes.
• An optional user namespace for the render worker. renderWorker.userNamespace.enabled runs the worker with hostUsers: false and adds CAP_SYS_ADMIN and CAP_SYS_CHROOT inside that namespace only, so Chromium can sandbox itself under the RuntimeDefault seccomp profile on clusters where no node profile can be installed. It needs Kubernetes 1.33 or later, containerd 2.0 or later and kernel 6.3 or later, and the worker refuses to start if the pod still shares the node's user namespace. Off by default.
• Connector origins in the web app's policy. connectorOrigins in the instance configuration adds up to 32 exact HTTPS origins to the served web app's connect-src and changes nothing else. Use it where the ingress cannot replace response headers; see configuration.
• Enterprise sign-in. OIDC handling is stricter, and enterprise sessions gain scoped provider logout with back-channel logout endpoints; see enterprise identity.
• Web app releases without restarting Work. An optional release-pointer mode serves immutable web app folders from one volume. It is off by default, and turning it on for an existing instance needs a one-time reviewed rollout; see IMMUTABLE-SHELL-RELEASES.md.
• Deployment tooling. Qualified web app deployment requests, resumable publication, bounded guard reads and validation of signed catalog resources in private cohorts.

1.1.1 migrations

Four SQL migrations since 1.1.0, bringing the maintained history to 60 files:

• 0067_oidc_logout.sql
• 0068_provisioning_scope.sql
• 0069_fleet_attribution.sql
• 0070_service_credential_expiry.sql

1.1.1 images

The release workflow built, signed and published both images from tagged source 9fddbf2f. The render worker came from the v1.1.1 tag push. The server came from a server-only run on main after its emulated arm64 build failed twice, so its signing identity ends in refs/heads/main. The release's release-source-images.json records the verified digests:

Both are multi-platform indexes for linux/amd64 and linux/arm64. The record does not claim native arm64 runtime qualification.

node scripts/vendor-content-resolver.ts --write
pnpm run repin-engine --apply
pnpm run verify:engine-pin
pnpm run typecheck

node scripts/yunohost-release.ts --ynh-rev 1 --shell-url https://lolli.li/lolly-web-1.1.1-ynh1.tar.gz --shell-sha256 bc78012aa407983ecc818e63be98ae1b45ed7db1dcad3f4c8d4ffe0c371116c1 --out ABS_NEW_ARTIFACT_DIRECTORY

1.1.0

The shared release is published as Work v1.1.0 and Lolly web-v1.1.0. Work's tag is b17800561df9a1e39cc4befce986a20fa1c7f661 and the Lolly web tag is 0359d8106bccbd1da56b5552605199f0bf705472. Lolly's desktop and mobile releases were held. Its tagged installation guide, deployment options and documentation index describe it as released.

Engine and core versions describe their own contracts and are not reset to the product version, and Lolly's private workspace package version is separate from the desktop product version. engine-pin.json carries the exact Lolly origin, packed content hashes and schema hashes; content-resolver-pin.json carries the same resolver origin. The maintained producers generate both.

The Work server uses that unmodified engine and core. The Chromium worker is a separate image, qualified with the same signed Lolly web app and catalog, and stays optional and off by default. The release workflow published both server and worker tags as 1.1.0, and the chart uses that application version for both default image tags and the migration Job; production installations should select the qualified immutable digests.

What 1.1.0 carried

The matched Lolly source includes the Design hierarchy and presentation work, responsive editor fixes, provider-reference catalog admission, export-error propagation, complete delivery validators, transition token bindings, the reviewed Strip Data 1.3 metadata cleanup, and the reviewed source navigation, emoji popover and number field styling. Work keeps its signed per-caller catalog, content coding verification, publication readiness, governed providers, collaboration and public delivery update helpers. The shared version records a matched application release: it does not turn on a new deployment, extra writable collaboration owners or an anonymous private-file service.

1.1.0 migrations

1.1.0 adds no SQL migration. The maintained history holds 56 files, through 0066_catalog_delivery_sequence.sql. Keep the generation and sequence tables, and do not reset their rows to make an old catalog look current.

1.1.0 images

The tagged Work source passed all five ordinary CI jobs, including native server and real Chromium worker qualification on Linux amd64, and the Helm and deployment checks passed. Release workflow attempt 2 published and signed both multi-architecture images from the exact tag. Its workflow source was 78e22f33dc8c3ba678133cbbfdeda6cbd771c3d6, separate from the tagged application source; the original failed attempts and the inherited source-artifact receipt are kept.

ghcr.io/lolly-tools/lolly-work-server@sha256:db96f0d0f84b81ec609a3816031bd7f78bbb2af87d36f49a6fef8a76c8a656ae
ghcr.io/lolly-tools/lolly-work-render-worker@sha256:8dbe45a9586f426c72cb87eb121da393e18c1074ff3ea5d886a39dceefdfbd5f

Anonymous access to the manifests, configuration and layer metadata was checked independently, as were both keyless signatures. The certificate issuer is https://token.actions.githubusercontent.com and the identity is https://github.com/lolly-tools/lolly-work/.github/workflows/release.yml@refs/heads/main. The release's source and image record lists the platform digests. Linux amd64 and arm64 images are published; native arm64 runtime qualification is open. Both GHCR packages are public.

node scripts/vendor-content-resolver.ts --write
pnpm run repin-engine --apply
pnpm run verify:engine-pin
pnpm run typecheck

node scripts/yunohost-release.ts --ynh-rev 3 --shell-url https://lolli.li/lolly-web-1.1.0-ynh3.tar.gz --shell-sha256 8bc8121a68e6fee6dda3902ed48d5e2669353bcfd101ca3822990235a2099376 --out ABS_NEW_ARTIFACT_DIRECTORY

sudo yunohost app install https://github.com/lolly-tools/lolly-work_ynh/tree/583cdc4af5322e683991a548428859b79084db2d