Releases

This documentation describes dqx 1.1.0.

bash

dqx version        # what you are running
dqx self-update    # what is current

What changed

Note: version releases in the 0.x.y range may introduce breaking changes.

minor: Create a project from a recipe: dqx init and the scaffold registry — laravel, qore-works-business and qore-cms — including for coding agents through MCP
minor: A repository is a full URL, per repository, so a project can span Bitbucket and GitHub at once
minor: Documentation for four audiences, with dqx docs opening it locally and a published site carrying the release it documents
minor: One place the binary lives: install.sh, latest.json and the binaries published together, so dqx self-update reads the same host the docs do
minor: dqx healthchecks finds compose probes that can never pass — a quoted test: exits 127 for ever and up --wait believes it
minor: dqx images pins the image tags of services that keep data on disk, and --outdated says when a pin has fallen behind
minor: dqx update-images refreshes the house images this machine already has, and never fetches a version line it does not run
minor: notes: in the config are printed after a successful install — what a person still has to do that no command can
minor: dqx adopt reads a project's init SQL for the schemas and the user no .env mentions, and stops overwriting declared MySQL server settings
minor: dqx version --where says which of the three dqx installs is answering, and bun run link:release goes back to the released one without downloading it again

major: One committed config drives four local backends — docker, ddev, lerd and herd — chosen per project
minor: Every project served at once behind a reverse proxy dqx owns: no fixed host ports, one certificate, no port collisions
minor: Install a project from nothing, and adopt an existing one of any dialect — v1, v2, v3 or no dq tools at all
minor: The daily verbs on every backend — shell, artisan, composer, npm, test, db, logs, xdebug — and dqx switch to move a project between them
minor: dqx doctor and dqx info: what is wrong with the machine or the project, in facts a developer and a coding agent read the same way