conductor/docs/RELEASE_NOTES_v1.0.0.md

Conductor v1.0.0 Release Notes

Conductor v1.0.0 is the first production application release. It delivers the initial supported feature set without changing the canonical project-document format.

Release identity

Item	Value
Application version	v1.0.0
Source tag	v1.0.0
Container	gitea.skeletonworks.online/vwiebe/conductor:v1.0.0
Supported container platform	Linux/AMD64
Project-document schema	0.1.0

Application and project-schema versions are independent. Existing valid schemaVersion: "0.1.0" projects remain the supported format in Conductor v1.0.0; this release does not require a project-document migration.

Highlights

• Visual and JSON authoring over one canonical project document.
• Eleven supported UI components with multi-page authoring and published deep links.
• REST actions, runtime request templates, typed variable declarations, response bindings, and Preview execution.
• Anonymous, Basic, Bearer, API-key header, and API-key query authentication for REST actions.
• Encrypted server-side stored credentials with opaque project references.
• Default-deny outbound proxy policy, bounded responses, safe errors, and sanitized execution history.
• Local administrator/user accounts, secure sessions, first-run administrator setup, and immutable public or restricted application snapshots.
• A hardened single-container production service with persistent SQLite state, health checks, generated-key requirements, backup, verified restore, upgrade, and rollback procedures.
• Public self-hosting documentation plus SkeletonWorks setup, backup, and restore integration.

Install and operate

• New independent installations: Installation Guide
• Application administration: Administrator Guide
• Project authoring and use: User Guide
• Backup, restore, upgrade, and rollback: Production Operations
• Security and recovery: Administrator Guide and Production Operations

Conductor ships with no default credentials. Production browser access requires HTTPS because authentication and setup cookies are marked Secure.

Upgrade from v0.1.0-rc.1

1. Create a verified backup and copy it off-host.
2. Preserve the existing .env, especially CONDUCTOR_SECRET_KEY and CONDUCTOR_SESSION_KEY.
3. Change the pinned image version to v1.0.0.
4. Pull and recreate the service.
5. Verify health, sign-in, a saved project, and a published deep link.

The project schema remains 0.1.0, so the application-version promotion does not require rewriting saved project documents. Keep the pre-upgrade image reference and matching backup until the upgrade has passed its smoke tests.

Principal limitations

• The v1.0.0 production container target is Linux/AMD64 only.
• SQLite supports one Conductor application instance; active/active replicas are not supported.
• Authentication uses local accounts; OIDC/SSO is planned after v1.0.0.
• Roles are global admin and user; custom roles and per-application assignments are not implemented.
• Advanced workflows, transforms, expression languages, retries, and action graphs are deferred.

See v1.0.0 limitations for the complete boundary.

Published artifacts

Artifact	Identity
Source commit	498003f83d7b7bba2cd4387a48428b32b8b16667
Versioned image	gitea.skeletonworks.online/vwiebe/conductor:v1.0.0
Source-correlated image	gitea.skeletonworks.online/vwiebe/conductor:git-498003f83d7b
OCI index digest	sha256:0c2db6bce31d81ad94df6a369eced714c6f291250789848803154985e5886a61
Linux/AMD64 manifest	sha256:02899719e7992f56d8880dc73250ff4d4739665d8ff7912386e770b646f94126

The source tag and container are publicly accessible without registry credentials. The image records application version v1.0.0, the source commit above, SBOM/provenance attestations, and the non-root conductor runtime user.