v0.2.1

Requires the core everybody actually runs.

This module pinned api v0.2.0 while the published core was v0.6.0 — four minors of drift, and the same for auth at v0.3.1 against v0.6.0.

A real application never noticed, because MVS lifts api to the highest requirement in the graph. The cost was ours: GOWORK=off go test ./... is the pass this repo treats as the real signal, precisely because a workspace masks a wrong requirement — and it was validating this module against a core three or four minors old. It also means a fresh go get of this module brought api v0.2.0 with it unless the consumer pinned the core themselves.

api v0.6.0 is a breaking change — App.FileSystem() and Context.disk moved onto interfaces declared in api/app, which gets the AWS and Google Cloud SDKs out of the core — and it is a pin change here: nothing outside api and media named the concrete types. Verified by building and testing every module standalone after the bump.

Where miniredis appears it is unified at v2.38.0, which was skewed against tasker.

This repository also has a CI workflow for the first time. The three that existed were written as though the monorepo were one repository, filtering on paths that do not exist in a per-module checkout, so none had ever run.