Skip to content

docs(changelog): 1.9.0 - #452

Open
msgwing wants to merge 1 commit into
mainfrom
release/1.9.0
Open

msgwing wants to merge 1 commit into
mainfrom
release/1.9.0

Conversation

@msgwing

@msgwing msgwing commented Sep 20, 2026

Copy link
Copy Markdown
Owner

CHANGELOG entry for the work merged since v1.8.0 (2026-08-29), about three
weeks ago. Verified against git log v1.8.0..HEAD and the merged PRs, not
recalled:

  • setup-postfix-relay.sh and the new msgwing/ansible-role-postfix-relay
    repo, plus the SYSTEM-MTA.md sender-rewrite docs they replace.
  • The zerosmtp-check --explain fix for enhanced-code/reply-code mismatch
    (fix(check): refuse --explain match when reply code contradicts the corpus (#423) #432).
  • main's required status checks restored from 11 example linters to all
    29 real gates - confirmed against gh api repos/msgwing/ZeroSMTP/branches/main/protection.
  • Wiki.js app coverage, community-contributed TrueNAS/Zabbix device data,
    Xerox 027-779, the check-facts device-panel invariant, zerosmtp-mcp 1.0.3,
    MCP Registry auto-publish + Dockerfile, the VS Code extension scaffold,
    and the re-measured ALTERNATIVES.md.

Next: tag v1.9.0 once this merges, to trigger draft-release.yml.

…d checks restored

Three weeks since v1.8.0: setup-postfix-relay.sh and a companion Ansible
role automate the sender-rewrite step that was causing real "not owned by
user" rejections; zerosmtp-check --explain no longer matches an enhanced
code against a contradicting reply code; main's required status checks are
restored to all 29 real gates instead of the 11 example-language linters
that were silently the only ones enforced for ten days.
@msgwing
msgwing enabled auto-merge (squash) September 20, 2026 13:05

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant