StackExchange/dnscontrol
1
1
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2025-12-09 05:36:27 +08:00
Code Issues Projects Releases Packages Wiki Activity

Merge 5b08ce4d24 into 0ae4acc3e4

Browse source
This commit is contained in:
Tom Limoncelli 2025-12-08 16:54:37 +00:00 • committed by GitHub
commit d16a32b422
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 13 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
.goreleaser.yml
View file

@ -157,12 +157,24 @@ release:
draft: true draft: true
prerelease: auto prerelease: auto
mode: append mode: append
header: |
Greetings DNS fans!
Thanks to all contributors involved in this release! This is a community project and we couldn't do it without all of your contributions!
Sincerely,
--Tom Limoncelli
## Monthly video call!
Everyone is invited to the __Monthly DNSControl Community Video Conference Call__ on the 3rd Monday of each month. Join whether you are a new user with questions or an experienced developer that wants to discuss DNSControl internals... or anything in between! Meeting details on [GitHub Discussions](https://github.com/StackExchange/dnscontrol/discussions).
footer: | footer: |
## Deprecation warnings ## Deprecation warnings
> [!WARNING] > [!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 > - **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
> - **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. > - **NAMEDOTCOM, OPENSRS 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.
## Install ## Install