The 53 upstream files this fork changed were marked on 2026-09-19
("Modified by Coffey Labs in 2026 for INBUXA."), but nothing kept it up:
the next edit to an upstream file could ship without the notice.
tools/notice-check.mjs does for the console what inbuxa-server's
tools/fork/notice-check.py does for the server: it diffs against the
upstream release this fork is built on (v1.0.11, dc462b1), takes every
changed file whose header names Stalwart Labs as a copyright holder, and
fails when one lacks the notice. --fix adds it under the license line
(npm run notice:check / notice:fix). Renames count; a pure move doesn't.
A new notices job runs it on every push and pull request, whatever
BUILD_ON says: seconds, no npm install.
Today: clean, 52 changed upstream files, all marked.
The 53 upstream files this fork changed were marked on 2026-09-19
("Modified by Coffey Labs in 2026 for INBUXA."), but nothing kept it up:
the next edit to an upstream file could ship without the notice.
tools/notice-check.mjs does for the console what inbuxa-server's
tools/fork/notice-check.py does for the server: it diffs against the
upstream release this fork is built on (v1.0.11, dc462b1), takes every
changed file whose header names Stalwart Labs as a copyright holder, and
fails when one lacks the notice. --fix adds it under the license line
(npm run notice:check / notice:fix). Renames count; a pure move doesn't.
A new `notices` job runs it on every push and pull request, whatever
BUILD_ON says: seconds, no npm install.
Today: clean, 52 changed upstream files, all marked.
The 53 upstream files this fork changed were marked on 2026-09-19
("Modified by Coffey Labs in 2026 for INBUXA."), but nothing kept it up:
the next edit to an upstream file could ship without the notice.
tools/notice-check.mjs does for the console what inbuxa-server's
tools/fork/notice-check.py does for the server: it diffs against the
upstream release this fork is built on (v1.0.11, dc462b1), takes every
changed file whose header names Stalwart Labs as a copyright holder, and
fails when one lacks the notice. --fix adds it under the license line
(npm run notice:check / notice:fix). Renames count; a pure move doesn't.
A new `notices` job runs it on every push and pull request, whatever
BUILD_ON says: seconds, no npm install.
Today: clean, 52 changed upstream files, all marked.
jcoffey-dev
changed title from Merge pull request 'Domains › Deliverability: what other mail servers see of this one' (#83) from feat/deliverability-page into main to CI: fail when a changed upstream file lacks the AGPL 5(a) notice2026-10-06 01:38:23 +00:00
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.
The 53 upstream files this fork changed were marked on 2026-09-19
("Modified by Coffey Labs in 2026 for INBUXA."), but nothing kept it up:
the next edit to an upstream file could ship without the notice.
tools/notice-check.mjs does for the console what inbuxa-server's
tools/fork/notice-check.py does for the server: it diffs against the
upstream release this fork is built on (v1.0.11,
dc462b1), takes everychanged file whose header names Stalwart Labs as a copyright holder, and
fails when one lacks the notice. --fix adds it under the license line
(npm run notice:check / notice:fix). Renames count; a pure move doesn't.
A new
noticesjob runs it on every push and pull request, whateverBUILD_ON says: seconds, no npm install.
Today: clean, 52 changed upstream files, all marked.
The 53 upstream files this fork changed were marked on 2026-09-19 ("Modified by Coffey Labs in 2026 for INBUXA."), but nothing kept it up: the next edit to an upstream file could ship without the notice. tools/notice-check.mjs does for the console what inbuxa-server's tools/fork/notice-check.py does for the server: it diffs against the upstream release this fork is built on (v1.0.11,dc462b1), takes every changed file whose header names Stalwart Labs as a copyright holder, and fails when one lacks the notice. --fix adds it under the license line (npm run notice:check / notice:fix). Renames count; a pure move doesn't. A new `notices` job runs it on every push and pull request, whatever BUILD_ON says: seconds, no npm install. Today: clean, 52 changed upstream files, all marked.Merge pull request 'Domains › Deliverability: what other mail servers see of this one' (#83) from feat/deliverability-page into mainto CI: fail when a changed upstream file lacks the AGPL 5(a) notice