feat(deps): bump github.com/libdns/libdns from 0.2.3 to 1.1.1

[dependabot]

Bumps github.com/libdns/libdns from 0.2.3 to 1.1.1.

Release notes

Sourced from github.com/libdns/libdns's releases.

v1.1.1

What's Changed

• Support CAA Values with embedded spaces by @​gucci-on-fleek in libdns/libdns#179
• Clarify SetRecords behaviour by @​gucci-on-fleek in libdns/libdns#187

Full Changelog: libdns/libdns@v1.1.0...v1.1.1

v1.1.0

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 libdns/libdns#174
• Introduce AtomicErr (close #175) by @​mholt in libdns/libdns#176

New Contributors

• @​NicolaiSoeborg made their first contribution in libdns/libdns#174

Full Changelog: libdns/libdns@v1.0.0...v1.1.0

v1.0.0

After 5 years, libdns v1 is here! This is a breaking change from versions prior to the 1.0 betas that introduces a more flexible, capable Record abstraction and clarifies a lot of semantics regarding how the APIs should be expected to work. We've defined more types and helper functions as well. This should help eliminate confusion regarding use, and provide more consistency across providers and with more diverse record types (RR-types).

Please read the new godoc for details!

The core interfaces (AppendRecords(), DeleteRecords(), etc.) are actually unchanged in terms of signature. The main changes in 1.0 are:

• Record is now an interface, not a struct type.
• RR is a new struct type that is similar to what Record was, but is a generic representation of a "Resource Record".
• Many new types corresponding to DNS RR types, such as TXT, MX, Address (for A/AAAA), CNAME, and more, all which implement the Record interface.
• Calling RR.Parse() returns the corresponding RR-type-specific struct with parsed fields.
• Provider-specific data can be included in ProviderData fields, but should not be relied upon for correctness.
• Much more explicit documentation regarding specific behaviors and edge cases, considering a variety of record types.

⚠️ Provider packages will need to update to conform with the new APIs and semantics, but based on feedback from early adopters, the changes are generally straightforward. We just ask that you document what you do and do not support, if your package cannot be fully compliant with the APIs for one reason or another.

Thank you to all who contributed to make this possible! It definitely was a community effort. We hope you enjoy the new clarified, stabilized APIs.

What's Changed

• Establish relative record name convention (fix #12) by @​mholt in libdns/libdns#28
• Fix example code by @​balki in libdns/libdns#87
• Add ZoneLister interface to list available zones (close #52) by @​Xinayder in libdns/libdns#98
• Document exact semantics of DNS interfaces by @​gucci-on-fleek in libdns/libdns#152
• All-new Record abstraction and exported APIs by @​mholt in libdns/libdns#153

New Contributors

• @​mholt made their first contribution in libdns/libdns#28
• @​balki made their first contribution in libdns/libdns#87

... (truncated)

Commits

• 6071c1f Clarify SetRecords behaviour (#187)
• 6ab812e Support CAA Values with embedded spaces (#179)
• 6be5766 Introduce AtomicErr (close #175) (#176)
• 933c390 Clarify SetRecords example/doc (#174)
• 9b97177 Clarify ProviderData field
• 5058491 Minor docs enhancements
• e0df105 Create RR.ProviderData (close #119) (#169)
• 10a2b0b Make all zero values have .RR().Data == "" (#166)
• db2a2dd Don't use .@ for relative names in [SRV|ServiceBinding].RR() (#165)
• 8fedb4f Support 2-label SRV names (fix #163) (#164)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)