libdns v1.1.0 loosens the required semantics of some operations; the previous semantics remain valid, and this release adds no new user-facing features, so providers are under no obligation to upgrade.

Previously, providers were required to apply the changes in SetRecords atomically (unless documented otherwise); now, atomic updates are optional (but still recommended). For providers who still wish to adhere to the more stringent requirements, they may signal this by returning libdns.AtomicErr, which will indicate that SetRecords failed and that no changes were applied. Returning any other error value indicates that an indeterminate number of the requested changes (between 0 and n - 1) were applied.

What's Changed

• Clarify SetRecords example/doc by @NicolaiSoeborg in #174
• Introduce AtomicErr (close #175) by @mholt in #176

New Contributors

• @NicolaiSoeborg made their first contribution in #174

Full Changelog: v1.0.0...v1.1.0