Repository navigation
v0.5.9
Dexaflow v0.5.9
A 0.x (pre-1.0) build — SemVer carries the maturity, there is no separate
alpha/beta, and the pre-alpha series ended at v0.0.1 (ADR 0037). APIs and
on-disk shape may still evolve between minor versions; -rc.N tags are release
candidates gated by the E2E suite. Install this exact release with:
curl -fsSL https://raw.githubusercontent.com/dexadata/dexaflow/v0.5.9/install.sh | LEOFLOW_VERSION=v0.5.9 shA bare
curl … | shinstalls the latest stable release (/releases/latest
excludes pre-releases), so on a pre-release page it would NOT give youv0.5.9.
LEOFLOW_VERSIONmust sit on theshside of the pipe (notcurl) — a
VAR=x curl … | shprefix sets the var forcurlonly, soinstall.shwould
not see it and would fall back to latest-stable.
Added
- Deactivate a user through the API.
PATCH /api/v2/users/{user_id}with
{"is_active": false}deactivates an account of the caller's tenant, and
truereactivates it; it needswrite:user(admin). A deactivated user's
sessions and API tokens stop working at their next request, their token
renewal is refused and they cannot sign in. Deactivating ends those
credentials for good: the user's API tokens are revoked, and a session it had
stays refused after a reactivation, so the user signs in again (migration
058 addsusers.sessions_valid_after). The change and a
user.deactivateoruser.activateaudit entry are written in one
transaction. An admin cannot deactivate their own account, and a user of
another tenant answers 404. Until now deactivation was a direct database
change (#960); changing roles and passwords through the API is #2229. dexaflow init --dbtscaffolds a DAG with an embedded dbt project. It
writes the hybrid shape the dbt guide teaches: adag.pywith Python tasks
arounddbt_group("transform"), adexaflow.yamlthat declares the group
and installsdbt-coreanddbt-duckdb, and a small duckdb project with
noprofiles.yml, sodexaflow literuns it with no warehouse to set up
(#1002). The same project ships asexamples/dbt_hybrid(#1003), and the
Python reference now documents thedexaflowauthoring package with
dbt_group(#1004).compile --buildnames the base image it resolved. Withbase_image
unset, the base depends on the CLI running the build: a release pins its
own versioned base, a development build takes the moving line. The build
now prints which one it took and why, or the filebase_imagecame from
(#1255).dexaflow buildchecks the whole workspace first and has--dry-run.
An invaliddexaflow.yamlin any project now fails the run before anything
is built, instead of after every project before it.--dry-runprints each
dag id with the image it would be built as and stops. A blank registryurl
is now treated as no registry, asdeployalready did (#1121).pkg/admission: the dispatch admission hook contract (ADR 0100). The
public types of a hook that sees each task attempt after the server's own
checks and before its agent token is minted, and admits, changes, holds or
refuses it. The server already runs such hooks and counts their outcomes in
dexaflow_dispatch_admission_total{outcome}; the way to install one (the
webhook and its configuration, or an embedding server) follows in a later
release. (#2177)- Admission webhook. Set
execution.admission.webhook.url(Helm
execution.admission.webhook.url) and every task attempt is sent to your
endpoint before it gets a credential or a pod. The endpoint admits it,
changes its node selector, tolerations, priority class, labels or
annotations, holds it, or refuses it with a reason the task shows. A broken
endpoint holds attempts (up to 15 minutes) unless
execution.admission.fail_openis on. See
Admission hooks. (#2177) - Add MCP tools of your own without forking the server. The new public Go
packagepkg/mcpis the coredexaflow-mcpis built from: it serves the
stock tools, resources and prompts, andmcp.AddToolregisters a tool
declared with the official MCP Go SDK types. The handler receives the
control-plane client of the caller (the request's bearer on HTTP, the
process token on stdio), so an added tool keeps the stock tools' blast
radius. A newdexaflow://capabilitiesresource reports the server version,
its transport, which tool groups are on and every tool it serves. The
dexaflow-mcpbinary keeps its flags and behavior (#2178). - A versioning and support policy. The new Project, Versioning and support
page states what a 0.x patch may contain (ADR 0068), that the previous minor
gets security fixes for 8 weeks after the next minor ships, that a
deprecated feature is removed no earlier than two minors later and never in
a patch, and that the names from before the rename keep working with no
removal date. SECURITY.md and RELEASING.md now say the same. (#1556) pkg/serverruns the control plane from your own Go program (ADR 0099,
#2176).server.Run(ctx)behaves exactly asdexaflow-server: it mirrors the
DEXAFLOW_*andLEOFLOW_*names, readsDEXAFLOW_CONFIGand the
environment, and serves untilctxis done;server.ExitCodekeeps the
binary's exit codes. The shipped binary is now a thin caller of it. Options
to replace a component (log sink, XCom backend, authenticator, trusted
issuer, UI, admission hook) follow in later releases. A program that imports
the module reports the module version it requires as its version.server.WithAdmissioninstalls an admission hook compiled into your own
binary (ADR 0099, ADR 0100, #2176, #2177). A program built onpkg/server
registers any number ofpkg/admissionhooks; they run in registration
order, before the webhookexecution.admission.webhook.urlconfigures, under
the same timeout, fail mode, change checks and breaker.server.WithLogSinkstores task logs with a sink of your own (ADR 0099,
#2176). The new public packagepkg/logsinkholds the contract (Sink,
LogWriter,Ref,Eventand the optionalLineWriter,Resumerand
MarkerSink); a program built onpkg/serverpasses its sink and the
logs.backendkeys are ignored. The sink also serves every read of a task
log.server.WithXComBackendkeeps XCom values in a store of your own
(ADR 0099, #2176). The new public packagepkg/xcomstoreholds the contract
(Backend,Entry,ErrNotFoundand the optionalBatchBackend); a
program built onpkg/serverpasses its backend, which replaces Redis or
the embedded Postgres store for values while Redis keeps the live log tail.server.WithUIServerserves a web UI of your own (ADR 0099, #2176). A
program built onpkg/serverpasses aserver.UIServer, which the server
mounts in place of the embedded UI, behind the same session check and
sign-in redirect.server.WithAuthenticatorandserver.WithTrustedIssuerplug your own
sign-in into the control plane (ADR 0099, #2176). The new public package
pkg/authnholds the contracts (Authenticator,User,Credentials,
TrustedIssuer,Identityand their errors). Password sign-in goes to the
authenticator from options while the sessions Dexaflow mints keep working,
and the server clears the scope and deploy-audience fields of the users it
returns. A trusted issuer from options takes the handoff from the origins it
lists.server.WithConfigFilenames the config file of a control plane run from
your own program (ADR 0099, #2176), in place ofDEXAFLOW_CONFIG; the
DEXAFLOW_*environment still applies on top of it.
Changed
- The bundled UI refreshes DAG, run and task-instance state every 5 seconds
instead of 30 whenui.autoRefreshIntervalSecondsis unset. Set it to30
to keep the old cadence; see the upgrade note (#1196). - New runs and task instances get time-ordered UUIDv7 keys. Migration 057
makesdexaflow_uuidv7()the default ofdag_runs.idand
task_instances.idinstead of the randomgen_random_uuid(). New keys
append to the end of the primary key index. On a large table Experiment 9
measured the random key at a third fewer inserts per second, a third more
WAL per row and a 27% larger index. Existing ids, the column type and the foreign keys are
unchanged, and the down migration restores the old default. A UUIDv7 id
carries the millisecond its row was created. (#525, ADR 0098) pkg/client:ClientInterfaceandClientWithResponsesInterfacegain
the user update methods.PatchUser,PatchUserWithBodyand their
WithResponsevariants are new methods of the generated interfaces. Code
that only calls the client is unaffected; a type of your own that implements
one of these interfaces (a hand-written mock, for example) must add the new
methods, or embed the interface, to keep compiling. (#960)- Every Go package under
pkg/now follows the public API compatibility rule
(ADR 0099, #2176): no breaking change in a patch release, and a removal only
in a minor after a deprecation of one minor. The API compatibility check runs
apidiffon all of them, not onlypkg/clientandpkg/dagspec. - golang.org/x/crypto moves to v0.58.1-0.20261009181718-2f1f834330b2, the
first revision that carries the fix for GO-2026-5932 (x/crypto/openpgp).
Dexaflow does not import that package; the bump keeps the filesystem
vulnerability scan green.
Fixed
- An attempt's cached XCom spec no longer outlives the attempt when one of its
XCom calls was loading the spec at the moment the attempt reported its end:
the load's result is no longer put back in the cache after the end dropped
the entry (#1616). - A task's
poolindag.pynow reaches the engine (#2227). The compiler
dropped it, so on a cluster with pools on every task was admitted against
default_pool, whatever pool it named.poolis now captured from the
operator, from@task(pool=...)and fromdefault_args, likepool_slots.
Once a DAG is redeployed, its tasks that name a pool are gated by that pool;
a pool the tenant has not defined does not gate them (under
server.pools_read_onlythey fall back todefault_pool). Tasks in
default_poolproduce the samedag.jsonas before. install.shinstalls the MCP server. The release archive has carried
dexaflow-mcpsince the MCP server shipped, but the installer copied only
the CLI, server and agent, so acurl | shinstall had no MCP server and
said nothing about it. It now installsdexaflow-mcp(with its
leoflow-mcplink) whenever the archive holds it (#976).- The leader-settling gate reads when a sweep started, not when it ended.
A pod reconciler sweep whose pod list was taken before a re-acquisition of
leadership, but which finished after it, could open the reapers' settling
gate with data from before the new leadership. The sweep is now stamped
with its start (#917). - The OpenAPI spec documents the
503every protected route can return.
Since the control plane answers503withRetry-Afterwhen a credential
cannot be checked during a store outage, a client generated from the spec
had no way to model it. Every operation that takes a bearer token now lists
the sharedAuthUnavailableresponse, andpkg/clientcarries it (#1098). - GKE Workload Identity behind the task NetworkPolicy: the docs now name
both metadata addresses (#1089). The guides told you to re-allow only
169.254.169.254/32, which is what GKE Dataplane V2 needs; a cluster with
network policy enforcement reaches the metadata server on the node at
169.254.169.252port 988, so tasks there got no token. External secrets,
the cluster validation guide, the installation guide and the
taskNetworkPolicy.allowMetadataEgressvalue now list both, each still a
single host. No chart behavior changed. - Task NetworkPolicy on Cilium: the node's own link-local addresses were not
blocked (GHSA-38p3-564h-jxp7). On GKE Dataplane V2 the task policy's
169.254.0.0/16block did not cover addresses served by the task pod's own
node, so a task reached the node's metadata server at169.254.169.252:988
and got a Workload Identity token even withallowMetadataEgressempty. GKE
with Calico was not affected. On Cilium set
taskNetworkPolicy.blockPrivateNetworks=true, which closes that path, and
re-allow the internal services your DAGs call with
taskNetworkPolicy.extraEgress. The install NOTES now warn when the chart
sees Cilium and that setting is off; the docs say the same. - Clicking a task in the grid opened the task page instead of the task
instance, so its logs could not be reached (#2295). The Airflow 3.3 grid
and graph open a task instance only when the grid summary carries the run's
dag_version_number, which the server did not send, so every click landed
on the run-less task page, which has no Logs tab. The summaries now carry it,
the grid runs carry theirdag_versions(the grid's version markers show
again), and the DAG details carryis_favorite, so the star in the DAG page
header shows whether the DAG is starred. - The docs name the operators that compile but cannot run.
ExternalTaskSensor,ExternalTaskMarker,TriggerDagRunOperatorand
LatestOnlyOperatorneed the Airflow metadata database, which a task pod
does not have, so they fail on their first attempt. The operators page now
lists them with the error each one raises and a workaround, the DAG
authoring list of unsupported constructs namesTaskGroup, and the
connector compatibility planning note no longer says sensors are rejected. - The DAG authoring list of unsupported Airflow constructs is complete and
current. It now namesEmptyOperator,chain(),Label, setup and
teardown tasks, a module-levelVariableimport,@task.bash,
PythonSensor,timedeltaoperator arguments, timetables and the trigger
rules Dexaflow refuses, says thatdepends_on_past,wait_for_downstream
andpriority_weightare ignored today, gives a workaround for each, and
links the issue that plans its support. It no longer says deferrable
operators fail at run time (they are refused at compile), that Jinja is
never rendered (operator template fields are), or thatdefault_argsis
ignored (scheduling fields are read from it).
Security
-
oauthlib 4.0.1 in the data runtime image. The
py3.11-dataimage moves
oauthlib from 4.0.0 to 4.0.1, which fixes CVE-2026-49272
(GHSA-3jp2-3mrg-2vxc, HIGH): the device code grant of oauthlib's OAuth 2.0
provider issued a bearer token for anydevice_codesent with a known
client ID. The image only uses oauthlib as a client library (through
requests-oauthlib and databricks-sql-connector) and runs no OAuth provider,
so DAGs on earlier images were not exposed; the bump keeps the release scan
of the data image clean. Nothing else in the lock changes. -
klauspost/compress 1.20.2. The control plane moves the indirect
dependency from 1.19.2 to 1.20.2, which fixes GO-2026-6865, a panic on
two-block frames. The object store log sink reaches the affected zstd and
huff0 code when it writes and reads task logs.
Full commit log: v0.5.9-rc.2...v0.5.9
Artifacts are checksummed (SHA-256) and the checksums file is cosign-signed
(keyless). Verify with cosign verify-blob.