Say near the top that latest lags main, and by how long #282

Closed
opened 2026-09-04 20:02:42 +00:00 by jcoffey-dev · 0 comments
Owner

A fix announced as "live" on a closed issue means ihasmail.com, which deploys from main. It does not mean the image anybody has pulled — that is cut weekly, Mondays at 09:00 UTC, so between one Monday and the next main runs ahead of the newest release by up to a week.

That distinction was written down nowhere, and it confused the reporter on #174 this week. My wording caused it: three comments invited him to try changes that were merged and not yet published.

Placement. Above the "this file is for people working on ihasmail" line, rather than under Container images. The person who needs this is reading to decide whether to pull; by the time they reach that section they usually have. Container images gains the cadence as well, since "Published to GHCR on every release" says nothing about how often a release happens.

The hour is given as approximate deliberately — GitHub runs scheduled workflows best-effort and delays them when its queue is busy, which the release workflow's own comment already notes.

Docs only — no code, no strings, no catalogue changes.

Merged 2026-09-04 as coffey-labs/ihasmail@eca8468d84

Rebuilt from: GH Archive, git history, session transcript.

A fix announced as "live" on a closed issue means **ihasmail.com**, which deploys from `main`. It does not mean the image anybody has pulled — that is cut weekly, Mondays at 09:00 UTC, so between one Monday and the next `main` runs ahead of the newest release by up to a week. That distinction was written down nowhere, and it confused the reporter on #174 this week. My wording caused it: three comments invited him to try changes that were merged and not yet published. **Placement.** Above the "this file is for people working *on* ihasmail" line, rather than under **Container images**. The person who needs this is reading to decide whether to pull; by the time they reach that section they usually have. Container images gains the cadence as well, since "Published to GHCR on every release" says nothing about how often a release happens. The hour is given as approximate deliberately — GitHub runs scheduled workflows best-effort and delays them when its queue is busy, which the release workflow's own comment already notes. Docs only — no code, no strings, no catalogue changes. **Merged** 2026-09-04 as coffey-labs/ihasmail@eca8468d84c1 <sub>Rebuilt from: GH Archive, git history, session transcript.</sub>
This repo is archived. You cannot comment on issues.