Release: v1.0.0-rc-1 — the release candidate, and the breaking list is closed

:wagoe/user-http-handler is removed. It has thrown on init since it was deprecated, so nothing was running on it — use :wagoe/user-routes with the top-level :wagoe/http-handler.

Ten methods are dropped from the user repository ports. None of them had a caller. If you implement the ports by hand, delete them; wagoe.user.ports lists what remains.

An unknown :provider on :wagoe/cache or :wagoe/realtime now throws. It used to fall back to an in-process adapter, which is the worst possible failure: a typo in production ran a node-local cache or a node-local event bus across your cluster, and nothing said so.

Provider names were three vocabularies wearing one keyword. They are now :memory and :redis everywhere, and :db where a module has one. :in-memory, :redis-streams and :database warn until 2.0.

wagoe.jobs.shell.adapters.db/enqueue-in-tx! is deprecated — call wagoe.jobs.ports/enqueue-in-tx! on the queue component. The :wagoe/admin and :wagoe/auth-user-repository Integrant components are deprecated too; drop them from hand-written wiring, and keep :wagoe/admin in :active, which is still the module switch.

The local storage adapter let a caller escape :base-path. A key containing ../, or a symlink under the root, could read, write and delete outside it. Upgrade if you accept storage keys from users.

Signed download URLs were never verified. The route served the file without checking expires or signature, so a signed URL was a suggestion. It enforces both now; point :http-base-path at wherever you mount the routes. Those routes can also be mounted deliberately with :expose-http? true — they carry no authorization of their own, so the mounting application has to guard them.

Nine modules were documented, published, and absent from a generated project’s deps.edn — jobs, events, push, realtime, reports, calendar, geo, audience and email. They ship in it now. Around that, the modules themselves:

The production image built and ran on JDK 17 while the installer demanded 21. One baseline now — Java 21 — held by a gate that reads the package names people actually install. Rebuild your images.

Every alias and launcher sets -Duser.timezone=UTC, so zone-less columns re-read in UTC instead of in whatever the host was set to. Push, geo and audience timestamps carried no timezone at all; a migration widens them on PostgreSQL and H2, and it assumes the stored values are UTC.

MySQL sessions also ignored their timezone and charset settings — a sql_mode MySQL 8 rejects aborted the rest of the session setup.

MySQL could not open a connection and SQLite reported every table as absent; SQLite was also handed PostgreSQL column types. Upgrade if you run either.

The S3 adapter threw on every S3-compatible endpoint, so MinIO, Spaces and the like could not be used despite being named as supported. Set :endpoint and it works.

Eight libraries are marked incubating: published, usable, and outside the breaking-change guarantee. wagoe list modules shows the tier, and so do the library pages. Knowing which eight matters more at a release candidate than at any point before it.

Expired sessions are now pruned — :wagoe/session-pruner deletes them 30 days after expiry; set :enable-pruning false to keep the rows. And worker mode actually runs jobs: enable :wagoe/jobs {:provider :memory}, modules contribute handlers, and :workers {:count 0} gives you a web-only node.

The Render and Fly blueprints built a container that served nothing. Both build the root Dockerfile now and set ERROR_REPORTING_PROVIDER=no-op. The dev image ignored its own JAVA_OPTS — -Xmx512m never applied and it ran on 1960MB; rebuild if you use resources/conf/dev/Dockerfile.

34 coordinates across 34 deps.edn files are up to date, jedis 8 and the Google Cloud bundle among them. Re-pin if you override any. bb upgrade-outdated was also under-reporting drift: it read an index that lags, which hid the H2, MySQL, PostgreSQL and SQLite drivers, and it no longer offers prereleases.

Two build-side fixes worth naming because they affect what you get: a locally built library jar could carry a previous build’s namespaces — jar cleans first now, and the published artifacts were checked and are unaffected. And a pre-release could again outrank the release it precedes; pre-releases are cut from the next minor, and both bb bump and the publish guard refuse a patch pre-release.

docs-site/ is gone — the published site is built from the same .adoc sources, and this was a second renderer nothing ran. The per-engine query, metadata and utils namespaces under adapters.database are removed along with config-factory; build adapters with factory/db-context.

All 31 artifacts bumped to v1.0.0-rc-1 to maintain lockstep versioning.

Re-run the installer to pick up the latest release:

Coming from a beta, work through this list: