Backport of #372 to 2026.x. Patch by @StefanSa, applied exactly as attached to #372 (he made it against this branch). Main gets a port in its own PR.
With DNS management already Automatic, adding a record type to publishRecords was saved but queued no DNS task, so the new records were never published. The workaround was switching the domain to Manual and back. An Automatic to Automatic save now queues one DNS task for the newly enabled record types. Removing a type deletes nothing, the same set in another order queues nothing, and new domains, Manual to Automatic and the DKIM paths behave as before.
A second commit adds the Coffey Labs modification notice to domain.rs, which notice-check now requires on this branch.
Checked on this branch:
cargo test -p jmap --lib registry::mapping::domain: 9 passed
cargo fmt --all --check, the four fork checks and changelog-check.py: clean
Backport of #372 to 2026.x. Patch by @StefanSa, applied exactly as attached to #372 (he made it against this branch). Main gets a port in its own PR.
With DNS management already Automatic, adding a record type to `publishRecords` was saved but queued no DNS task, so the new records were never published. The workaround was switching the domain to Manual and back. An Automatic to Automatic save now queues one DNS task for the newly enabled record types. Removing a type deletes nothing, the same set in another order queues nothing, and new domains, Manual to Automatic and the DKIM paths behave as before.
A second commit adds the Coffey Labs modification notice to `domain.rs`, which notice-check now requires on this branch.
Checked on this branch:
- `cargo test -p jmap --lib registry::mapping::domain`: 9 passed
- `cargo fmt --all --check`, the four fork checks and `changelog-check.py`: clean
With DNS management already Automatic, adding a record type to
publishRecords was saved but queued no DNS task, so the new records
were never published (the workaround was Manual and back to Automatic).
An Automatic to Automatic save now queues one DNS task for the record
types that are newly enabled. Removing a type deletes nothing, and the
same set in another order queues nothing. New domains, Manual to
Automatic, and the DKIM paths behave as before.
Task planning moves into schedule_dns_tasks, with unit tests for each
transition. Applied as attached to #372.
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.
Backport of #372 to 2026.x. Patch by @StefanSa, applied exactly as attached to #372 (he made it against this branch). Main gets a port in its own PR.
With DNS management already Automatic, adding a record type to
publishRecordswas saved but queued no DNS task, so the new records were never published. The workaround was switching the domain to Manual and back. An Automatic to Automatic save now queues one DNS task for the newly enabled record types. Removing a type deletes nothing, the same set in another order queues nothing, and new domains, Manual to Automatic and the DKIM paths behave as before.A second commit adds the Coffey Labs modification notice to
domain.rs, which notice-check now requires on this branch.Checked on this branch:
cargo test -p jmap --lib registry::mapping::domain: 9 passedcargo fmt --all --check, the four fork checks andchangelog-check.py: clean