Since 2026.9.22 the deploy pins ihasmail from registry.coffeylabs.org
(config.IhasmailRepository), but the public e2e still looked for the
ghcr.io name. Its sed matched nothing, so it failed with "does not pin
ihasmail to a dated release: none" on a deploy that was correct. The check
now uses the registry name, kept in one variable beside a note to keep it
in step with the config.
Since 2026.9.22 the deploy pins ihasmail from registry.coffeylabs.org
(config.IhasmailRepository), but the public e2e still looked for the
ghcr.io name. Its sed matched nothing, so it failed with "does not pin
ihasmail to a dated release: none" on a deploy that was correct. The check
now uses the registry name, kept in one variable beside a note to keep it
in step with the config.
Since 2026.9.22 the deploy pins ihasmail from registry.coffeylabs.org
(config.IhasmailRepository), but the public e2e still looked for the
ghcr.io name. Its sed matched nothing, so it failed with "does not pin
ihasmail to a dated release: none" on a deploy that was correct. The check
now uses the registry name, kept in one variable beside a note to keep it
in step with the config.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Since 2026.9.22 the deploy pins ihasmail from registry.coffeylabs.org
(config.IhasmailRepository), but the public e2e still looked for the
ghcr.io name. Its sed matched nothing, so it failed with "does not pin
ihasmail to a dated release: none" on a deploy that was correct. The check
now uses the registry name, kept in one variable beside a note to keep it
in step with the config.