Skip to main content
Version: v5.7.1

OpsChain GA Release 5.7.1

OpsChain 5.7.1 is a generally available release, published on 2026-11-14. Every release is listed on the releases index.

Fixed​

  • Session refresh and step-up keep working during a quiesce under the core AuthService name. While the system is quiesced, limepoint.core.v1.AuthService Refresh, Elevate and BeginIDPStepUp used to answer 503 system quiesced although the same verbs under opschain.api.v2.AuthService passed; both names now pass the write barrier exactly alike, and Login stays refused under either. Reference: opschain docs cli/admin-platform-quiesce.
  • A stored-workflow address no longer falls into local mode silently. opschain runs create workflow <project>/<code> with no server targeted (no --server, no OPSCHAIN_SERVER, no active server context) used to answer --env is required, hiding the cause; it now refuses by name — the address names a stored workflow on a server and nothing targets one — and says how to target it. The local lane's own --env refusal now says which lane it is in.
  • A node path no longer falls into local mode silently. opschain runs create change <node-path> (an argument with a / and a projects, environments, assets or entities segment) with no server targeted used to answer --env is required; it now refuses by name. An action name (deploy, web:deploy) still runs locally. Reference: opschain docs cli/runs-create-change.
  • --project is no longer ignored in local mode. opschain workflows list, actions list and actions show with --project and no server targeted used to list the repository's catalog as if the flag were absent; they now refuse the flag by name. Reference: opschain docs cli/workflows-list.
  • The admin commands report a broken contexts file instead of "a server is required". opschain admin login/logout and every admin fleet command now surface an undecodable contexts.json or an active context that is not defined in it, exactly like every other command.

Changed​

  • The provider services now come from LimePoint's go-core library. The secrets provider, transport provider, image build provider and image registry, model provider, model usage, GitHub integration, JSM integration and inbound-webhook services are served by github.com/limepoint/go-core/providers over the provider stores that already came from it, with OpsChain supplying the licence gate and its limits, the audit recorders, the platform vault and the estate reads (changes, projects, git remotes, the change-governance block) the lanes need. Every existing route answers exactly as before — the opschain.api.v2 procedures, their payloads, the 404-on-deny posture, typed error details, audit events and the write-time credential pin are unchanged — and the same handlers are additionally available under their core names (limepoint.core.v1.SecretsProviderService, TransportProviderService, ImageBuildProviderService, ImageRegistryService, ModelProviderService, ModelUsageService, GitHubIntegrationService, JsmIntegrationService, InboundWebhookService) at the same /api/v2 mount; the OpenAPI document gains those procedures and nothing else. No setting, migration, command or flag changes.
  • Every home-dependent surface names its home and how it was chosen. opschain context (bare, show, list) ends with Home: <path> (from --home | from OPSCHAIN_HOME | the per-OS default) and, when the home has no contexts.json, says so (Context: local (local mode — no contexts.json in <home>)); -o json|yaml of context and config gains home and home_source. opschain login and opschain context use name the contexts.json they wrote; server start names its home and its configuration file (or that none exists and built-in defaults apply) before the listen line; server backup/restore/migrate, admin database backup/restore, runner and agent name the home they operate on. A machine with several homes can now tell which one a command used. Reference: opschain docs cli.
  • One refusal for "no server is targeted". Every command that needs a server and resolves to local mode now says what needed the server, why the target is local — the home and whether it has a contexts file, or --local — and the three ways to target a server: --server <url>, OPSCHAIN_SERVER, or opschain context use <name>. Exit codes are unchanged. Reference: opschain docs cli.
  • The authorisation engine, the policy and security-role services, server administration authorisation and the step-up floor now come from LimePoint's go-core library. The path-trie authorisation engine (the compiled snapshot every decision rides, the role grants, the list filter, the selector index) is built from github.com/limepoint/go-core/authz, with OpsChain's git-remote identity policy and trust tiers registered onto it as extensions; the AuthorisationPolicyService procedures (policies, rules, links, assignments, the rule-path catalog) are served by that library, the security-role grant procedures (ListSecurityRoleGrants, GrantSecurityRole, RevokeSecurityRole, ConfirmSecurityRoleGrant) by github.com/limepoint/go-core/securityadmin, which also carries the /admin authorisation gate, and the step-up verb floor and the rule-demand guard by github.com/limepoint/go-core/stepup. Every existing route answers exactly as before — the opschain.api.v2 procedures, their payloads, visibility, 404-on-deny posture, typed error details and audit events are unchanged — and the same handlers are additionally available as limepoint.core.v1.AuthorisationPolicyService and limepoint.core.v1.SecurityRoleService at the same /api/v2 mount; the OpenAPI document gains those procedures and nothing else. No setting, migration, command or flag changes.
  • The identity services now come from LimePoint's go-core library. Sign-in (local, OIDC, GitHub, LDAP), sessions and API keys, MFA factors and step-up, the login throttle, the first-boot administrator, and the user, group, identity-provider and service-account services are built from the github.com/limepoint/go-core/identity module instead of OpsChain's own copies. Every existing route answers exactly as before — the opschain.api.v2 UserService, GroupService, IdentityProviderService and AuthService procedures, their payloads, error details and the session cookie are unchanged — and the same services are additionally available under their core names (limepoint.core.v1.UserService, GroupService, IdentityProviderService, AuthService) at the same /api/v2 mount; the OpenAPI document gains those procedures and nothing else. No setting, migration, command or flag changes.
  • The shared platform libraries now come from LimePoint's go-core library. Encryption envelopes and secret ciphers, the blob stores, the migration lock and database maintenance, the request log and request-origin middleware, idempotency keys, security counters and API usage, the broadcast bus, log masking, the secrets backends (AGE file, AWS Secrets Manager, Azure Key Vault, OpenBao) with the secret-reference grammar and provider economy, the secrets, transport, image, model, GitHub, JSM and inbound-webhook provider stores, provider usage and the notification connectors are built from the github.com/limepoint/go-core modules instead of OpsChain's own copies. Nothing changes functionally in this release: every route, payload, command, flag, setting and migration is the same as in 5.7.0.
  • The event spine, the correlation-chain helpers and the SIEM/OTLP export now come from the go-core library's events module. The SIEM forwarder's formatters (Splunk HEC, syslog/CEF, OTLP/HTTP traces and provider-usage metrics) and the correlation scope the agent plane and the agent SDK share are built from github.com/limepoint/go-core/events, with OpsChain's naming (the opschain.* trace attributes, the CEF device identity, the Splunk row fields) supplied to the library, so every forwarded payload is byte-for-byte what 5.7.0 sent. Beside the existing opschain.api.v2.EventService, the shared limepoint.core.v1.EventService (ListEvents, GetEvent, GetEventStats) is mounted at /api/v2 and reads the same events through the library's generic record — an addition only: every existing route, payload, event type and event payload is unchanged, the OpsChain event service remains the surface the CLI and GUI use, and no setting or migration changes. Reference: opschain docs api-v2, integrations-siem.
  • Licence verification now comes from the go-core library. The signed licence document and its Ed25519 envelope, the canonical form every signature is checked over, the embedded LimePoint keyrings, the pack manifest and pack bundle formats, the online-licence refresh loop and the entitlement resolution are built from github.com/limepoint/go-core/licence, with OpsChain's own limits, feature vocabulary, evaluation footprint and revocation denylist registered onto it. Every licence already issued verifies exactly as before, every limit and feature gate answers as before, licence_status, opschain admin licence and the opschain.api.v2 licence procedures are unchanged, and no setting, migration, command or flag changes. Reference: opschain docs entitlements, ops/licensing-runbook.
  • The evidence ledger's hash chain, the runner and agent enrolment mechanics and the notification matching rules now come from the go-core library. The governance evidence ledger's row hashing, chain verification and re-anchoring are built from github.com/limepoint/go-core/ledger under OpsChain's own anchor vocabulary, so every stored row and anchor verifies exactly as before; the runner and agent session ladder (challenge, signed response, short-lived bearer), the sealed stateless session bearer, the registration-token credential grammar and fingerprint come from github.com/limepoint/go-core/enrol under the same prefixes and key context, so a token minted by 5.7.0 is accepted by 5.7.1; the notification subscription vocabulary, the condition and attribute-predicate matching, the cadence resolution and the delivery sweeper's retry ladder, route plan and outcome come from github.com/limepoint/go-core/notify. Nothing changes functionally: every route, payload, command, flag, setting, token format, hash and migration is the same as in 5.7.0.
  • The retention engine now comes from the go-core library. The leader-run retention job's sweep loop, batching and leadership fencing, the export-before-delete archive (the sealed tar object, its manifest and the read-back verification), the missing-blob withholding and the sweep evidence are built from github.com/limepoint/go-core/retention, with OpsChain's data classes — each class's horizon from the retention: block, its SQL in both store dialects, the legal-hold exemptions, the artefact tombstone, the scheduler, recommendation, evidence-ledger and broadcast callbacks — injected as the catalogue. Nothing changes functionally: the same classes sweep in the same order, the same retention:sweep and warn:retention:blob_missing events carry the same payloads, the archives keep the opschain-retention-archive/v1 manifest, and every setting, metric, notice and command is the same as in 5.7.0. Reference: opschain docs retention.
  • The reference documentation server now comes from the go-core library. The embedded reference tree and learning path are loaded, validated, indexed and searched by github.com/limepoint/go-core/refdocs with OpsChain's own vocabulary injected — the page kinds, the pack-entitlement spelling, the guide families, the lesson numbering, the generated learning-path index and the curated index groups — so opschain docs, opschain learn, opschain docs export and every /api/docs response serve byte-identical pages, index groups, search results and raw page bytes, verified page by page against the pre-extraction loader. Nothing changes functionally: every route, payload, command, flag, page and slug is the same as in 5.7.0.
  • The migration ledger, the encryption key lifecycle, the structured logger and the server's listener now come from the go-core library. The migration integrity ledger and its boot verification, the newer-schema rollback gate and opschain admin database migrations / opschain server migrate are built from the library's lineage-aware migration runner (github.com/limepoint/go-core/store/migrate) with OpsChain's migration set as its primary lineage — the same goose_db_version and migration_ledger tables, markers and wording, and no new table on an existing database; opschain admin encryption status|reencrypt and the key-set boot gate from github.com/limepoint/go-core/store/encryptionkeys with OpsChain's encrypted-column inventory; the structured logger, the log-file rotation and the log-line correlation ids from github.com/limepoint/go-core/telemetry (every attribute in the order it always had); the TCP listener, the TLS/h2c serve loop and the health probe writer from github.com/limepoint/go-core/server. Nothing changes functionally: every route, payload, command, flag, setting, log line and migration is the same as in 5.7.0.
  • The admin plane's gate, the leader lease, the backup manifest, the support bundle and the quiesce barrier now come from the go-core library's server kit. The admin-token gate every /admin and /api/admin route is served behind (the static token of the single-node posture, the browser fallback and the typed retired-token refusal), the replica heartbeat and the named leases the scheduler elects its leader and holds its shards and run drives with, the backup-info manifest with its content digest and the four verify-restore checks, the support bundle's collector, manifest and tar.gz envelope, and the estate-wide write barrier a quiesced system holds are built from github.com/limepoint/go-core/server (adminplane, leaderlease, backup, supportbundle, quiesce) with OpsChain's own shapes supplied: its route tables and refusals, its leases and scheduler_replicas tables, the volatile tables and blob references its manifest names, its diagnostics item list, and the exempt routes and read-only procedures its barrier admits. Every admin endpoint, backup manifest, support bundle and quiesce verb answers exactly as before in every posture (the local lane, the SQLite server and the PostgreSQL server), and the server-side support bundle's diagnostics (and the text of any failed fetch) now also pass through the log masker seeded with the secret values the server resolved at start — the provisioned keys, each OPSCHAIN_PREVIOUS_KEYS element, PGPASSWORD, OPSCHAIN_BLOBSTORE_SECRET_ACCESS_KEY, the static admin token, the store DSN password, the blob store's secret access key, the LDAP bind password and the vault block's secret keys, each masked both as written and in its JSON-escaped form (a password containing &, < or " included), never connection parameters such as PGHOST or PGUSER or values shorter than eight characters — so a diagnostic that echoed one carries ****** in its place; the CLI-side bundle applies no masker. No setting, migration, command or flag changes.
  • Every release carries its own record in the repository. make release-record writes docs/releases/<version>/ at the cut: the build identity of every platform (module, commit, build instant, toolchain, whether the binary was obfuscated — never an obfuscation seed) and the acceptance record (the integration test report and the capability suites' evidence table and walks), committed beside the tag with the Install page. Build identity and acceptance evidence are records, not secrets, so nothing is copied into a password vault for a normal cut; only an obfuscated cut's seeds are kept outside the repository, as the licensing runbook describes. The 5.7.0 record is the first entry. Reference: README.release-train.md, opschain docs ops/licensing-runbook.
  • The release train cuts the documentation site's version for every GA release. Step 8, make docs-site-cut, runs the site's own one command per release in the opschain-docs-private checkout (DOCS_SITE_DIR, on staging with a clean tree; the step branches docs/<version>-cut off it): sync every served page, the OpenAPI document, the sidebar trees and the Academy track pages from this repository; freeze the release notes from the changelog section under the scrub gate; snapshot the version; build the whole site; commit on the cut branch. A version already cut is re-cut with --refresh so the Install page carries the manifest the public publish wrote; an identical re-cut commits nothing; internal and pre-release tags skip by name. The docs repository's process is a PR into staging and a human promotion from staging to the production branch main, so the step never pushes and the train's closing notice names the push and the PR as the after-steps. Reference: README.release-train.md (step 8, "after the train" step 5). The suite-evidence verifier reads a CI run's artifact once (a skipping nightly's last_green attestation no longer re-downloads it) and release notes past GitHub's 125,000-character body limit are cut at a line boundary with a pointer to this file — both found by the v5.7.0 cut and in that release's train.