Commit 9bd9b11
authored
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4&size=40){kind=avatar}
Bump github.com/libdns/libdns from 1.0.0-beta.1 to 1.1.0 (#2)
Bumps [github.com/libdns/libdns](https://github.com/libdns/libdns) from
1.0.0-beta.1 to 1.1.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/libdns/libdns/releases">github.com/libdns/libdns's
releases</a>.</em></p>
<blockquote>
<h2>v1.1.0</h2>
<p>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.</p>
<p>Previously, providers were <strong>required</strong> to apply the
changes in <code>SetRecords</code> atomically (unless documented
otherwise); now, atomic updates are <strong>optional</strong> (but still
recommended). For providers who still wish to adhere to the more
stringent requirements, they may signal this by returning
<code>libdns.AtomicErr</code>, which will indicate that
<code>SetRecords</code> failed and that no changes were applied.
Returning any other error value indicates that an indeterminate number
of the requested changes (between 0 and <em>n</em> - 1) were
applied.</p>
<h2>What's Changed</h2>
<ul>
<li>Clarify <code>SetRecords</code> example/doc by <a
href="https://github.com/NicolaiSoeborg"><code>@NicolaiSoeborg</code></a>
in <a
href="https://redirect.github.com/libdns/libdns/pull/174">libdns/libdns#174</a></li>
<li>Introduce AtomicErr (close <a
href="https://redirect.github.com/libdns/libdns/issues/175">#175</a>) by
<a href="https://github.com/mholt"><code>@mholt</code></a> in <a
href="https://redirect.github.com/libdns/libdns/pull/176">libdns/libdns#176</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a
href="https://github.com/NicolaiSoeborg"><code>@NicolaiSoeborg</code></a>
made their first contribution in <a
href="https://redirect.github.com/libdns/libdns/pull/174">libdns/libdns#174</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/libdns/libdns/compare/v1.0.0...v1.1.0">https://github.com/libdns/libdns/compare/v1.0.0...v1.1.0</a></p>
<h2>v1.0.0</h2>
<p>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).</p>
<p><strong><a href="https://pkg.go.dev/github.com/libdns/libdns">Please
read the new godoc for details!</a></strong></p>
<p>The core interfaces (<code>AppendRecords()</code>,
<code>DeleteRecords()</code>, etc.) are actually <em>unchanged</em> in
terms of signature. The main changes in 1.0 are:</p>
<ul>
<li><a
href="https://pkg.go.dev/github.com/libdns/libdns#Record"><code>Record</code></a>
is now an interface, not a struct type.</li>
<li><a
href="https://pkg.go.dev/github.com/libdns/libdns#RR"><code>RR</code></a>
is a new struct type that is similar to what <code>Record</code> was,
but is a generic representation of a "Resource Record".</li>
<li>Many new types corresponding to DNS RR types, such as <a
href="https://pkg.go.dev/github.com/libdns/libdns#TXT"><code>TXT</code></a>,
<a
href="https://pkg.go.dev/github.com/libdns/libdns#MX"><code>MX</code></a>,
<a
href="https://pkg.go.dev/github.com/libdns/libdns#Address"><code>Address</code></a>
(for A/AAAA), <a
href="https://pkg.go.dev/github.com/libdns/libdns#CNAME"><code>CNAME</code></a>,
and more, all which implement the <code>Record</code> interface.</li>
<li>Calling <a
href="https://pkg.go.dev/github.com/libdns/libdns#RR.Parse"><code>RR.Parse()</code></a>
returns the corresponding RR-type-specific struct with parsed
fields.</li>
<li>Provider-specific data can be included in <code>ProviderData</code>
fields, but should not be relied upon for correctness.</li>
<li>Much more explicit documentation regarding specific behaviors and
edge cases, considering a variety of record types.</li>
</ul>
<p>:warning: 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.</p>
<p>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.</p>
<h2>What's Changed</h2>
<ul>
<li>Establish relative record name convention (fix <a
href="https://redirect.github.com/libdns/libdns/issues/12">#12</a>) by
<a href="https://github.com/mholt"><code>@mholt</code></a> in <a
href="https://redirect.github.com/libdns/libdns/pull/28">libdns/libdns#28</a></li>
<li>Fix example code by <a
href="https://github.com/balki"><code>@balki</code></a> in <a
href="https://redirect.github.com/libdns/libdns/pull/87">libdns/libdns#87</a></li>
<li>Add ZoneLister interface to list available zones (close <a
href="https://redirect.github.com/libdns/libdns/issues/52">#52</a>) by
<a href="https://github.com/Xinayder"><code>@Xinayder</code></a> in <a
href="https://redirect.github.com/libdns/libdns/pull/98">libdns/libdns#98</a></li>
<li>Document exact semantics of DNS interfaces by <a
href="https://github.com/gucci-on-fleek"><code>@gucci-on-fleek</code></a>
in <a
href="https://redirect.github.com/libdns/libdns/pull/152">libdns/libdns#152</a></li>
<li>All-new Record abstraction and exported APIs by <a
href="https://github.com/mholt"><code>@mholt</code></a> in <a
href="https://redirect.github.com/libdns/libdns/pull/153">libdns/libdns#153</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/mholt"><code>@mholt</code></a> made
their first contribution in <a
href="https://redirect.github.com/libdns/libdns/pull/28">libdns/libdns#28</a></li>
<li><a href="https://github.com/balki"><code>@balki</code></a> made
their first contribution in <a
href="https://redirect.github.com/libdns/libdns/pull/87">libdns/libdns#87</a></li>
<li><a href="https://github.com/Xinayder"><code>@Xinayder</code></a>
made their first contribution in <a
href="https://redirect.github.com/libdns/libdns/pull/98">libdns/libdns#98</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/libdns/libdns/commits/v1.0.0-beta.1">https://github.com/libdns/libdns/commits/v1.0.0-beta.1</a></p>
<h2>What's Changed</h2>
<ul>
<li>Document exact semantics of DNS interfaces by <a
href="https://github.com/gucci-on-fleek"><code>@gucci-on-fleek</code></a>
in <a
href="https://redirect.github.com/libdns/libdns/pull/152">libdns/libdns#152</a></li>
<li>All-new Record abstraction and exported APIs by <a
href="https://github.com/mholt"><code>@mholt</code></a> in <a
href="https://redirect.github.com/libdns/libdns/pull/153">libdns/libdns#153</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/libdns/libdns/commit/6be57668e7bf10f6c31ab7ffcd7cc132766c1ee2"><code>6be5766</code></a>
Introduce AtomicErr (close <a
href="https://redirect.github.com/libdns/libdns/issues/175">#175</a>)
(<a
href="https://redirect.github.com/libdns/libdns/issues/176">#176</a>)</li>
<li><a
href="https://github.com/libdns/libdns/commit/933c3901a6335c74a2b0e5fdfafd5aaa06feed5c"><code>933c390</code></a>
Clarify <code>SetRecords</code> example/doc (<a
href="https://redirect.github.com/libdns/libdns/issues/174">#174</a>)</li>
<li><a
href="https://github.com/libdns/libdns/commit/9b97177ca13a3854fa43a4ff6471b2f485ce31b9"><code>9b97177</code></a>
Clarify ProviderData field</li>
<li><a
href="https://github.com/libdns/libdns/commit/505849161d82942aee7f711e5582ebab8a4f9dd6"><code>5058491</code></a>
Minor docs enhancements</li>
<li><a
href="https://github.com/libdns/libdns/commit/e0df105aed0e13a68e893367f93eabb73a558638"><code>e0df105</code></a>
Create RR.ProviderData (close <a
href="https://redirect.github.com/libdns/libdns/issues/119">#119</a>)
(<a
href="https://redirect.github.com/libdns/libdns/issues/169">#169</a>)</li>
<li><a
href="https://github.com/libdns/libdns/commit/10a2b0b2c222c51900827339aaf1e22f5cfd2528"><code>10a2b0b</code></a>
Make all zero values have <code>.RR().Data == ""</code> (<a
href="https://redirect.github.com/libdns/libdns/issues/166">#166</a>)</li>
<li><a
href="https://github.com/libdns/libdns/commit/db2a2dd0747a96049f1beaae42a8052c0214a186"><code>db2a2dd</code></a>
Don't use <code>.@</code> for relative names in
[SRV|ServiceBinding].RR() (<a
href="https://redirect.github.com/libdns/libdns/issues/165">#165</a>)</li>
<li><a
href="https://github.com/libdns/libdns/commit/8fedb4f57bfacc5abb64a8eff0b331dfea191181"><code>8fedb4f</code></a>
Support 2-label SRV names (fix <a
href="https://redirect.github.com/libdns/libdns/issues/163">#163</a>)
(<a
href="https://redirect.github.com/libdns/libdns/issues/164">#164</a>)</li>
<li><a
href="https://github.com/libdns/libdns/commit/5ab1d4de259f1eb914085c61784ad9176ea8e803"><code>5ab1d4d</code></a>
Document that provider-specific types are allowed (<a
href="https://redirect.github.com/libdns/libdns/issues/162">#162</a>)</li>
<li><a
href="https://github.com/libdns/libdns/commit/7fe2177d834c6ce3de17d14e3836da0fa4a6cc47"><code>7fe2177</code></a>
readme: Update more links to beta docs</li>
<li>Additional commits viewable in <a
href="https://github.com/libdns/libdns/compare/v1.0.0-beta.1...v1.1.0">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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)
</details>
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parent 46a317d commit 9bd9b11
2 files changed
+3
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
8 | | - | |
| 8 | + | |
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
241 | 241 | | |
242 | 242 | | |
243 | 243 | | |
244 | | - | |
245 | | - | |
| 244 | + | |
| 245 | + | |
246 | 246 | | |
247 | 247 | | |
248 | 248 | | |
| |||
0 commit comments