inbuxa/ihasmail-inbuxa
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Publish to INBUXA's own image, and don't release on a schedule yet

Browse Source 
Two things inherited from public ihasmail that became live the moment this
repository went public.

publish.yml pushed ghcr.io/coffey-labs/ihasmail -- the image every public
ihasmail install pulls. A release here would have published INBUXA's webmail
over it, which is the exact confusion SPEC 5 exists to prevent. It now
publishes ghcr.io/inbuxa/ihasmail-inbuxa.

release.yml cuts a release every Monday at 09:17 UTC, which public ihasmail
wants because it has users expecting one. This fork has none yet, and the
release triggers the publish, so on Monday it would have shipped an image
and mailed everyone watching about a product that has not shipped. Scheduled
runs now stop at the first job; a release can still be cut by hand, and the
weekly one comes back by removing one line.
This commit is contained in:
jcoffey-dev
2026-09-20 00:01:02 -07:00
parent a2ba7f5acd
commit 25763832f3
2 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/publish.yml
+5 -1
View File
@@ -63,7 +63,11 @@ env:
# Hardcoded rather than derived from github.repository: a registry path must
# be lowercase and the owner is spelled `Coffey-Labs`, so deriving it means
# remembering to lowercase it. This is the string the docs already name.
IMAGE: ghcr.io/coffey-labs/ihasmail
# inbuxa: this fork publishes to INBUXA's own path. Inherited from public
# ihasmail, which publishes ghcr.io/coffey-labs/ihasmail -- leaving that
# here would push INBUXA's webmail over the image every public ihasmail
# install pulls, which SPEC.md 5 exists to prevent.
IMAGE: ghcr.io/inbuxa/ihasmail-inbuxa
jobs:
# The version is worked out once and handed to both builds, so the two