For the installer's --webmail host (phase 2). An inbuxa-v tag's GitHub run gets a new files job, after publish:
It takes /app out of each architecture's image that was just published: inbuxa-webmail-linux-amd64.tar.gz, inbuxa-webmail-linux-arm64.tar.gz, and SHA256SUMS, attached to the Gitea release. That's the app the image runs, production node_modules included.
VERSION inside the tarball records what the image carries as IHASMAIL_VERSION.
A re-run replaces the assets. Uploads use HTTP/1.1 with retries. The job feeds report.
Checked locally by extracting the 2026.10.9-g62936ab image this way (3.4 MB tarball, 11 MB unpacked, no native addons) and running it with the host's Node 26 on loopback, files read-only as the installer will make them. /api/health answers ok with the right version, and the app serves. With IMMUTABLE=1 the webmail refuses writable app files, so the installer installs them root-owned and runs the webmail as its own user. actionlint is clean. It takes effect on the next inbuxa-v tag.
For the installer's `--webmail host` (phase 2). An `inbuxa-v` tag's GitHub run gets a new `files` job, after `publish`:
- It takes `/app` out of each architecture's image that was just published: **`inbuxa-webmail-linux-amd64.tar.gz`**, **`inbuxa-webmail-linux-arm64.tar.gz`**, and **`SHA256SUMS`**, attached to the Gitea release. That's the app the image runs, production `node_modules` included.
- `VERSION` inside the tarball records what the image carries as `IHASMAIL_VERSION`.
- A re-run replaces the assets. Uploads use HTTP/1.1 with retries. The job feeds `report`.
Checked locally by extracting the 2026.10.9-g62936ab image this way (3.4 MB tarball, 11 MB unpacked, **no native addons**) and running it with the host's Node 26 on loopback, files read-only as the installer will make them. `/api/health` answers `ok` with the right version, and the app serves. With `IMMUTABLE=1` the webmail refuses writable app files, so the installer installs them root-owned and runs the webmail as its own user. actionlint is clean. It takes effect on the next `inbuxa-v` tag.
An inbuxa-v tag's run now also takes /app out of each architecture's image it just published and attaches inbuxa-webmail-linux-amd64.tar.gz and inbuxa-webmail-linux-arm64.tar.gz to the Gitea release, with SHA256SUMS: what the installer's --webmail host runs under Node 26 with a unit of its own. It is the app the image runs, production node_modules included (none of them native); VERSION records what the image carries as IHASMAIL_VERSION. A re-run replaces the assets; uploads go over HTTP/1.1 with retries. Its result feeds the report to Gitea.
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.
For the installer's
--webmail host(phase 2). Aninbuxa-vtag's GitHub run gets a newfilesjob, afterpublish:/appout of each architecture's image that was just published:inbuxa-webmail-linux-amd64.tar.gz,inbuxa-webmail-linux-arm64.tar.gz, andSHA256SUMS, attached to the Gitea release. That's the app the image runs, productionnode_modulesincluded.VERSIONinside the tarball records what the image carries asIHASMAIL_VERSION.report.Checked locally by extracting the 2026.10.9-g62936ab image this way (3.4 MB tarball, 11 MB unpacked, no native addons) and running it with the host's Node 26 on loopback, files read-only as the installer will make them.
/api/healthanswersokwith the right version, and the app serves. WithIMMUTABLE=1the webmail refuses writable app files, so the installer installs them root-owned and runs the webmail as its own user. actionlint is clean. It takes effect on the nextinbuxa-vtag.