16 lines
2.0 KiB
Markdown
16 lines
2.0 KiB
Markdown
# Conductor v1.1.0
|
|
|
|
Conductor now hosts independently installed browser applications. Adding or updating an included app no longer requires patching Conductor source or rebuilding its image.
|
|
|
|
This release includes the finished home and Projects screens, the Included with Skeleton Works catalog, the approved default favicon, application-aware browser titles, optional published/installed app icons, and host API v1 for verified application packages.
|
|
|
|
A fresh installation has no seeded apps. Packages, icons, users, projects, publications and connections persist on the customer VM. API forwarding enforces declared routes, Conductor access/CSRF checks, fixed connection values and backend token boundaries. Social Scheduler 0.5.0 is the first package using this interface; a separate example demonstrates that the interface is generic.
|
|
|
|
Application version: 1.1.0. Canonical project schema: 0.1.0, unchanged. Platform: Linux/AMD64. Runtime: Node 24. Backup format: v2, adding installed app assets; the updated restore accepts old v1 backups as well.
|
|
|
|
Production dependency audit is clean after compatible runtime updates and a patched qs override for Express. The existing Create React App build toolchain still reports transitive development/build advisories. Its build tools are excluded from the production runtime; migration of that toolchain is a separate follow-up.
|
|
|
|
Read [Application packages](APP_PACKAGES.md) for the installer and API contract, and [Operations](OPERATIONS.md) for recovery. Current combined Conductor/Social Scheduler installations require the migration sequence in that guide. The old setup-conductor.sh is not an upgrade tool. SLICE12 and SLICE13 deliver the setup and existing-VM upgrade procedures.
|
|
|
|
Published release: [Conductor v1.1.0](https://gitea.skeletonworks.online/vwiebe/conductor/releases/tag/v1.1.0). Its entry records the exact source commit, image digests, artifact checksums and verified anonymous downloads. See [SLICE11](../SLICE11.md) for the completed work log. Customer-VM deployment remains a separate SLICE13 step.
|