The fix from #240 (#239) for the 2026 series, which :latest runs until 27.1 ships: on the DNS setup pages a valid DMARC or SPF record of the domain's own shows as "Your own record, valid" and counts toward "All set", instead of an amber mark about cached records.
Cherry-pick of the fix commit from main. Two conflicts, both from main-only work: ConnectDnsPage.tsx (main hides the record table when nothing is selected) and en.json (main's no-records strings). Kept only #239's lines.
Version 2026.10.26.9 with its CHANGELOG entry.
Checked locally on this branch: typecheck, lint, i18n:check, tests (964), changelog check, listen-ipv6 test, notice check, build.
The fix from #240 (#239) for the 2026 series, which `:latest` runs until 27.1 ships: on the DNS setup pages a valid DMARC or SPF record of the domain's own shows as "Your own record, valid" and counts toward "All set", instead of an amber mark about cached records.
- Cherry-pick of the fix commit from main. Two conflicts, both from main-only work: `ConnectDnsPage.tsx` (main hides the record table when nothing is selected) and `en.json` (main's no-records strings). Kept only #239's lines.
- `Version 2026.10.26.9` with its CHANGELOG entry.
Checked locally on this branch: typecheck, lint, i18n:check, tests (964), changelog check, listen-ipv6 test, notice check, build.
The DNS setup pages marked every published record that wasn't exactly
the suggested one as different, in amber, with a note about old records
in caches, and never reached "All set". A DMARC with the domain's own
report addresses, or an SPF with an extra include, is neither: the
admin chose it and it's valid.
The pages now judge DMARC and SPF with coreState from #237. A single
well-formed record of the domain's own gets a green badge ("Your own
record, valid"), counts toward the progress and "All set", and a note
says it can stay. The amber mark and its caching note stay for records
that really differ: two SPF records, a DMARC with no policy, an MX or
DKIM key elsewhere.
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 fix from #240 (#239) for the 2026 series, which
:latestruns until 27.1 ships: on the DNS setup pages a valid DMARC or SPF record of the domain's own shows as "Your own record, valid" and counts toward "All set", instead of an amber mark about cached records.ConnectDnsPage.tsx(main hides the record table when nothing is selected) anden.json(main's no-records strings). Kept only #239's lines.Version 2026.10.26.9with its CHANGELOG entry.Checked locally on this branch: typecheck, lint, i18n:check, tests (964), changelog check, listen-ipv6 test, notice check, build.