7 Commits

Include renames

Author	SHA1	Message	Date
jcoffey-dev	b6660554e6	Merge pull request 'CI: open an issue when upstream publishes a release not yet imported' (#15) from ci/upstream-watch into main ... Reviewed-on: #15	2026-09-22 23:23:02 +00:00
jcoffey-dev	a4b091578d	CI: fail when the upstream name appears in a new string literal ... tools/fork/name-check.py reads every string literal in crates/ (comments and test directories skipped) and fails on any that carries the upstream name without an entry in name-allowlist.txt. An upstream merge can bring such strings in without a conflict, so it runs on every push and PR. The first run found three the earlier sweeps missed, fixed here: the SMTP HELP reply pointed at upstream's website (now brand_url!), the event collector thread was named after upstream, and the FreeBSD default data path still said /var/db/stalwart/ where Linux already had /var/lib/inbuxa/. Two operator-visible defaults are allowlisted as open, pending a decision: the log file prefix and the SQL stores' default database and user.	2026-09-22 16:12:47 -07:00
jcoffey-dev	39df888412	CI: open an issue when upstream publishes a release not yet imported ... Reads metadata only: upstream's releases list from GitHub's API and the head of the upstream branch from Gitea's. Nothing of upstream's is fetched, so its history can't land here. Daily at 06:17 UTC.	2026-09-22 15:37:34 -07:00
jcoffey-dev	8846a280f1	ci: publish the image on tags, port the weekly release ... publish.yml replaces .github/workflows/publish.yml: on a v* tag it checks the tag equals v<brand_version!> and is on main, builds the linux/amd64+arm64 image in one buildx run (the Dockerfile already cross-compiles, so only its final stage goes through QEMU), pushes :<version> and :latest to the registry, links the package, and creates the tag's release if it has none. weekly-release.yml ports .github/workflows/release.yml: bump brand_version! through the contents API, then create the release and so the tag, which starts publish.yml. It only dry-runs until RELEASE_LIVE=1 and a RELEASE_TOKEN secret exist.	2026-09-22 09:56:32 -07:00
jcoffey-dev	b37d252660	ci: raise the Cargo target-dir limit to 60 GB ... The dev and test profiles together already take ~22 GB after one cold build, so the 25 GB limit would have wiped a warm cache within a build or two.	2026-09-22 08:45:15 -07:00
jcoffey-dev	1ee2e2a6a3	ci: persistent Cargo cache, run on either runner ... The build now mounts the named volume inbuxa-server-cargo at /cache and keeps CARGO_HOME and CARGO_TARGET_DIR there, so a push reuses the compiled dependency tree (RocksDB included) instead of rebuilding it from scratch. Both runners allow that one volume; each host keeps its own copy. With the cache in place the job moves to runs-on: light, so it can run on host2 as well. Cargo's parallelism now follows the job's CPU cap rather than the host's core count, and the target dir is dropped past 25 GB.	2026-09-22 07:59:35 -07:00
jcoffey-dev	29bcfecb80	ci: add Gitea Actions workflow ported from .gitlab-ci.yml	2026-09-21 22:45:05 -07:00