Organization Releases

Plan organization-wide promotion across self-hosted SteelEngine environments

Organization releases follow a Git branch and promote managed workspaces in a self-hosted SteelEngine organization together. Workspaces with their own Source Control connection release independently. Builders work in development; reviewers approve a fixed release; production supplies its own connections and data.

The target can deploy manually or automatically after verifying a merged promotion PR. Automatic deployment pauses when a release needs human acceptance. See Git Approval and Release Status for the supported scope. Complete blue/green infrastructure and trigger coordination remain separate.

Read This Guide by Role

ReaderStart hereOutcome
Sponsor or solution architectThis page and Blue/GreenAgree scope, ownership, and rollout boundaries
Kubernetes operatorKubernetes SetupPrepare isolated environments and a verified Helm configuration
Integration administratorIntegration BindingsConnect production accounts once and map required resources
Builder or reviewerGit PromotionUnderstand what a PR approves and what makes a release live
On-call engineerOperationsPrepare monitoring, rollback, and incident procedures

Availability

Availability refers to the reviewed repository version, not a guarantee about a published image or CLI package. Record the actual build installed during your pilot.

CapabilityReviewed status
Whole-workspace capture, review, commit and PRImplemented for active workflows and folder placement; works with workflow controls disabled
Individual workflow review through GitHubPaused in code; no environment opt-in. Existing protection and synchronization remain enforced
Signed file transfer, preflight, apply, activation, rollbackImplemented self-hosted API/CLI for the reviewed workflow profile; requires configuration and compatible workers
Credentials and provider settings assigned on the targetImplemented for supported workflow resources
One release covering the managed workspacesWorkflows and folders; unsupported content in managed workspaces blocks capture
Organization release PR and target verificationBackground branch checks and manual or automatic coordinated activation
Apps, table schemas, knowledge-base configuration, workspace docsTarget scope; adapters and end-to-end support are incomplete
Coordinated production blue/green cutoverPlanned; the current Helm chart does not implement this protocol
SteelEngine container or database upgradeCustomer-operated infrastructure change; separate from content promotion

The Organization Is the Release Boundary

Organization and workspace source control remain available at their existing boundaries. Workflow-specific authoring is paused:

ScopeWhat you control
OrganizationGitHub setup, a followed branch, deployment policy, promotion PRs, coordinated activation and rollback for managed workspaces
WorkspaceRepository, path and target-branch settings; capture all workflows, review exact files, commit and open a PR; synchronization and workflow deployment history
Workflow (legacy)Retained protections and approved revisions; individual authoring controls are unavailable

Organization releases require PROMOTION_ENABLED=true and valid self-hosted configuration. Pausing workflow authoring does not change which workspaces are included in organization releases.

Use the Workspace Source Control hub when a team needs its own cadence. Its repository, branch, PRs, and deployment history stay independent. The organization release settings show which workspaces are managed by the organization and which have their own connection.

On an organization-managed target, activation coordinates the participating workspaces in one operation. An independent receiving workspace synchronizes and deploys from its own branch and policy.

A protected workflow's approved snapshot can be included in an organization release. An unmerged workflow PR remains separate from that candidate. On a promotion-managed target, an individual workflow deployment must not bypass the organization release boundary.

A release must account for every managed source workspace. Unchanged workspaces remain in the inventory. Independent workspaces are excluded; an unsupported managed workspace blocks capture. If the managed scope changes after capture, prepare a new matching release before deployment.

Workspace names are labels. Stable logical identities link source workspaces and objects to their target equivalents, even when local database IDs or names differ. An existing production workspace must be deliberately adopted through a supported mapping procedure; a matching name is insufficient.

“Entire organization” means the supported, declarative product definitions across all its workspaces. It does not mean copying the development database or granting development users access to production.

Included in the target release modelRemains local to each environment
Workspace inventory and supported descriptive settingsOrganization memberships, access grants, SSO, billing, license, deployment identity
Workflow graphs, prompts, code, and supported metadataRunning executions, history, runtime counters, personal drafts
App layouts and supported application configurationSessions, visitor data, live application records
Table schemas and supported constraintsProduction rows, business data, database credentials
Knowledge-base configuration and source requirementsDocuments, embeddings, connector credentials, ingestion state
Supported workspace doc contentPrivate storage locations and environment-specific resource assignments
Logical connection roles and dependency requirementsOAuth grants, API keys, provider apps, secrets, account/channel/resource IDs

Supported configuration is an explicit allowlist. A URL or identifier is not automatically portable because it is non-secret. Production endpoints, Slack channels, provider tenants, and similar destinations need target-local bindings or a reviewed environment overlay.

One Candidate, Several Environments

The intended lifecycle is: edit in development, capture a complete organization candidate, open a promotion PR, validate the exact candidate, merge, prepare the target, then activate according to target policy. Staging and production use the same payload digest. Validation evidence is added without rebuilding the content from whatever development contains later.

Git stores reviewable definitions and requirements. An immutable digest identifies the release content. The target separately records the PR/commit that approved it, local binding revisions, the active generation, and the infrastructure build that ran it.

Responsibilities

OwnerResponsibilities
SteelEngineSerialize supported definitions; validate identity, trust, dependencies and assignments; retain audit evidence; coordinate content activation and rollback
Customer platform teamKubernetes, Helm, TLS, ingress, storage, Temporal, container rollout, backups, monitoring and recovery
Customer organization administratorSource/target mapping, repository access, target connections, review policy and release authority
Builders and reviewersAuthor changes, review impact, execute agreed validation and approve the exact release

The customer pipeline may orchestrate a container upgrade and an organization release together. It must still record separate results and recovery points for each. A successful Helm rollout is not proof that every workspace was promoted, and a successful content activation is not proof that traffic moved to green.

Before Agreeing a Production Date

Agree the complete workspace inventory, supported object kinds and tools, integration owners, data compatibility rules, and recovery objectives. Rehearse in isolated installations using the exact intended builds. Obtain evidence for organization-wide atomic activation and trigger ownership before describing the planned workflow as production-ready.

On this page