Skip to content

Bump github.com/libdns/libdns from 0.2.2 to 1.1.1 #1493

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
dependabot wants to merge 1 commit into from
Closed

Bump github.com/libdns/libdns from 0.2.2 to 1.1.1 #1493

dependabot wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 1, 2025

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

Release notes

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

v1.1.1

What's Changed

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

New Contributors

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

New Contributors

... (truncated)

Commits

Dependabot compatibility score

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)

@dependabot
Bump github.com/libdns/libdns from 0.2.2 to 1.1.1
20aa9db 
Bumps [github.com/libdns/libdns](https://github.com/libdns/libdns) from 0.2.2 to 1.1.1.
- [Release notes](https://github.com/libdns/libdns/releases)
- [Commits](libdns/libdns@v0.2.2...v1.1.1)

---
updated-dependencies:
- dependency-name: github.com/libdns/libdns
  dependency-version: 1.1.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Sep 1, 2025
@xxx7xxxx xxx7xxxx closed this Sep 2, 2025
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Sep 2, 2025

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/go_modules/github.com/libdns/libdns-1.1.1 branch September 2, 2025 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file go Pull requests that update Go code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@xxx7xxxx