Skip to content
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.

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

fix(deps): update module github.com/stackexchange/dnscontrol/v4 to v4.15.2 #140

Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 17, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/StackExchange/dnscontrol/v4 v4.15.1 -> v4.15.2 age adoption passing confidence

Release Notes

StackExchange/dnscontrol (github.com/StackExchange/dnscontrol/v4)

v4.15.2

Compare Source

Happy holidays, DNSControl Fans!

Another quick bugfix release. This is particularly important if you use the BIND provider.

Bug: BIND

In 4.15.1 a bug was introduced that made the BIND provider use the
same filename for all zonefiles. That is fixed in this release. As a
bonus, BIND joins the list of providers that can run concurrently.

Do not use 4.15.1 if you use BIND.

Possible bug: IGNORE() plus MYTHICBEASTS

We're tracking a bug that was reported involving IGNORE() with MYTHICBEASTS (https://github.com/StackExchange/dnscontrol/issues/3227). If you use any of the IGNORE*() functions, please push with caution.

It might affect other providers that use the diff2.ByZone() function call (AUTODNS, BIND, REALTIMEREGISTER, SAKURACLOUD) with a smaller change it will affect providers that use the diff2.ByRecordSet() function (AZURE, GCLOUD, GCORE, HUAWEICLOUD, NS1, POWERDNS, ROUTE53, TRANSIP).

If you use any of those providers, we can use your help! Please run the integration tests (https://docs.dnscontrol.org/developer-info/integration-tests) and report if they were successful or not. This release includes a new test that should trigger this bug: Integration test number 77 IGNORE w/change b3227

That's it!

Sorry for the releases right before most people are going on break! If you are concerned about other issues, the last v4.14.x release was very stable and is backwards compatible.

Best,

Tom

Changelog

Provider-specific changes:
Documentation:
Dependencies:
Other changes and improvements:

Deprecation warnings

[!WARNING]

  • REV() will switch from RFC2317 to RFC4183 in v5.0. This is a breaking change. Warnings are output if your configuration is affected. No date has been announced for v5.0. See https://docs.dnscontrol.org/language-reference/top-level-functions/revcompat
  • MSDNS maintainer needed! Without a new volunteer, this DNS provider will lose support after April 2025. See https://github.com/StackExchange/dnscontrol/issues/2878
  • NAMEDOTCOM and SOFTLAYER need maintainers! These providers have no maintainer. Maintainers respond to PRs and fix bugs in a timely manner, and try to stay on top of protocol changes.
  • get-certs/ACME support is frozen and will be removed without notice between now and July 2025. It has been unsupported since December 2022. If you don't use this feature, do not start. If you do use this feature, migrate ASAP. See discussion in issues/1400

Install

macOS and Linux
Install with Homebrew (recommended)
brew install dnscontrol
Using with Docker

You can use the Docker image from Docker hub or GitHub Container Registry.

docker run --rm -it -v "$(pwd):/dns" ghcr.io/stackexchange/dnscontrol preview
Anywhere else

Alternatively, you can install the latest binary (or the apt/rpm/deb/archlinux package) from this page.

Or, if you have Go installed, you can install the latest version of DNSControl with the following command:

go install github.com/StackExchange/dnscontrol/v4@​main

Update

Update to the latest version depends on how you choose to install dnscontrol on your machine.

Update with Homebrew
brew upgrade dnscontrol

Alternatively, you can grab the latest binary (or the apt/rpm/deb package) from this page.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Dec 17, 2024

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 1 additional dependency was updated

Details:

Package Change
golang.org/x/exp v0.0.0-20241210194714-1829a127f884 -> v0.0.0-20241215155358-4a5509556b9e

@fritterhoff fritterhoff added this pull request to the merge queue Dec 18, 2024
Merged via the queue into main with commit f80c9a2 Dec 18, 2024
1 check passed
@fritterhoff fritterhoff deleted the renovate/github.com-stackexchange-dnscontrol-v4-4.x branch December 18, 2024 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant