Back to Home

Versioning

Release Notes

Public versioning and release-train summary for the production SaaS surface.
Current release
2026.07.16
Artifact regeneration integrity train
Public posture
Hardened SaaS
Core value loop, control plane, compliance, and support surfaces aligned.
Cutover caveat
External gates remain
Provider validation and production approvals are tracked separately from repo-complete work.

Release Gate Evidence Map

A release train is public only when the evidence below is visible and separated from owner-controlled approvals.

Code, tests, and CI

Repo verified

Merged release work must point to passing API, worker, web, security, and release-bundle gates for the touched services.

Staging validation

Staging verified

Deployable changes must pass staging migrations, service health checks, external reachability, auth smoke, and live browser smoke.

Rollback and runbook

Repo verified

Release notes stay tied to rollback criteria, runbooks, and operational evidence so support can restore service safely.

External owner signoff

External required

Legal, provider, billing, and customer pilot approvals remain separate external gates before declaring production business readiness.

Release Timeline
The latest release trains that changed the public Dynafloxis product surface.

2026.07.16

Current

Artifact regeneration integrity train

July 16, 2026

Makes historical artifact remediation deterministic, observable, and safe after BPMN/SVG/VSDX generator upgrades.

  • Generated process artifacts now identify the dynafloxis-workflow-graph-v2 engine so stale v1 outputs can be selected precisely.
  • Standalone regeneration jobs expose and persist correlation IDs from queue request through worker progress and terminal replacement events.
  • Backfill verification waits for the exact correlated artifacts_complete event instead of treating an already-completed parent run as job completion.
  • Operators can explicitly refresh legacy-valid BPMN, SVG, and VSDX outputs for selected historical runs without rerunning source discovery.
  • Run-event filtering and indexed correlation metadata provide auditable completion, failure, and timeout evidence for concurrent regeneration jobs.
  • BPMN link events retain throw/catch direction, scoped pairing, compliant routing, and matching SVG/VSDX notation.

2026.06.30

Stable

Artifact fidelity and evidence alignment train

June 30, 2026

Locks dense BPMN/SVG/VSDX subprocess fidelity to the real discovered semantics and aligns public release narratives with the verified product surface.

  • Expanded subprocesses no longer invent fake parallel split and merge semantics when the discovered process is sequential.
  • BPMN, SVG, and VSDX outputs now preserve richer child node kinds and wrapped dense-sequence layouts inside subprocess bounds.
  • Subprocess gateway fallback/default paths now keep their default-flow markers, labels, and VSDX metadata across generated artifacts.
  • Authenticated artifact previews avoid frame-blocked HTML embeds, suppress browser-blocked payload text, and allow only route-scoped data fonts required by BPMN diagram rendering.
  • Artifact-only regeneration remains available by artifact type while refreshed release and implementation docs now match the live codebase.
  • Public release messaging now distinguishes repo-verified hardening from remaining external rollout and approval gates.

2026.06.22

Stable

Production hardening train

June 22, 2026

Turns the SaaS runtime into a release-readiness product surface rather than a discovery-only prototype.

  • Platform control plane now requires explicit mutation targets for subscription and support changes.
  • Compliance and evidence pages expose repo-verified gates separately from external approval blockers.
  • Slack delivery is live for run completed and run failed notifications with validated webhook preferences.
  • Help center is backed by maintained article data and support channels match real configured contact paths.

2026.06.20

Stable

Source and UX reliability train

June 20, 2026

Closed major scanner-agent and dashboard-shell gaps needed for serious staging usage.

  • Scanner-agent source setup and tenant-aware source flows were productized across API and web.
  • Dashboard and platform navigation gained stricter capability gating and mobile-safe route coverage.
  • Evidence connector and support-ticket flows received broader end-to-end browser protection.

2026.06.19

Stable

Release gate evidence train

June 19, 2026

Established the repo-backed compliance, readiness, and production gate baseline.

  • Release-gate evidence packs, readiness snapshots, and compliance guard scripts were formalized.
  • Billing, support, notification history, and tenant-isolation regressions were locked down in tests.
  • Public compliance and product evidence now map back to maintained source-of-truth docs.
Versioning Rules
How public release communication stays aligned with actual product readiness.

Marketing and public release notes track dated release trains so buyers and operators can see what changed without diffing code.

Repo-verified product work is listed separately from external cutover approvals, legal signoff, or provider-side validation.

Status, release notes, and public landing copy should always agree on the current release train and operational posture.

Related surfaces
Use these pages together when evaluating the current public release.