v0.1.3
Stop the offline connection tests depending on a local Redis
The pub/sub suite says 'without a server answering' but only reached that
state by nothing happening to listen on 6379. On a developer machine with
Redis running the warm-up subscribe succeeded, so the twelve tests passed for
the wrong reason; on CI nothing listens, ioredis retried, and all twelve hit
the 5s timeout — a failure the machine that wrote them could not reproduce.
enableOfflineQueue: false makes a command issued before the socket is up
reject at once instead of queueing, which is the same outcome whatever is
listening. The suite now runs in under a second either way, against a live
Redis or none.
One rejection had been surviving in the offline queue rather than being
raised; awaited now, so it is not reported as an unhandled error for the run.
Cover the connection before it reaches a server
The integration suites skip when nothing answers on 6379, which left the
whole non-network half untested: the status readers, the command dispatcher
and the error wiring — the part whose only job is to keep an error event
from taking the process down.
Declare the environment variables the generated config reads
Checked against @adonisjs/mail 10.4.0, whose configure() publishes the config
AND calls defineEnvVariables beside it. Mine wrote a config full of
env.get('QUEUE_STORE') and declared nothing, which is the half-installation
the hook exists to prevent: the application boots, the config asks the
environment for something nothing ever put there, and the fallback answers.
addEnvVars was already on ream's codemods and simply went unused.
Say that ream add sets this up, because it does now
Ship the configure hook ream add expects
ream add <pkg> installs, then imports <pkg>/configure and runs it. Nine
packages provided that hook and this one did not, so ream add left an
application with a provider registered and no config file for it to read —
falling back to a default that is rarely the one anybody wanted, silently.
The hook registers the provider and writes the config stub beside it, because
the two are one step: a provider without its file is not installed, it is half
installed.
Create the GitHub release from the publish workflow
A published version arrived with no notes: npm showed a number, GitHub showed
nothing, and the only way to learn what changed was to read a diff. The commit
messages already carry the reasoning, so the release is built from the commits
the tag contains rather than written twice.
Skips a pure version bump, leaves an existing release alone, and does nothing
when the run was not built from a tag. The job takes contents:write for this;
the workflow default stays read.
Changes since v0.1.2.