chore(deps): bump github.com/caddyserver/certmagic from 0.15.3 to 0.17.2

[dependabot]

Bumps github.com/caddyserver/certmagic from 0.15.3 to 0.17.2.

Release notes

Sourced from github.com/caddyserver/certmagic's releases.

v0.17.1

This release changes the OnEvent API in a slightly breaking way, so if you are using events, please check out the new doc: https://pkg.go.dev/github.com/caddyserver/certmagic#Config.OnEvent

The new API is more flexible and easier to use. We are also documenting the events in our README.

Some bug fixes and improved logging. Minimum version is now Go 1.18.

Full Changelog: caddyserver/certmagic@v0.16.2...v0.17.1

v0.16.2

This release primarily improves DNS challenges, making them more efficient and correct (mostly edge cases).

What's Changed

• Fix deadlock and improve efficiency for wildcard DNS challenges by @​mholt in caddyserver/certmagic@dce2de2
• Improve Windows CI cache by @​mohammed90 in caddyserver/certmagic#189
• Set EDNS0 to 1232 bytes per recommendation by @​mohammed90 in caddyserver/certmagic#188
• Use OverrideDomain when cleaning up DNS solver by @​gjung56 in caddyserver/certmagic#193

New Contributors

• @​mohammed90 made their first contribution in caddyserver/certmagic#189
• @​gjung56 made their first contribution in caddyserver/certmagic#193

Full Changelog: caddyserver/certmagic@v0.16.1...v0.16.2

v0.16.1

Minor enhancement allowing customization of the propagation delay/timeout for DNS challenge.

Full Changelog: caddyserver/certmagic@v0.16.0...v0.16.1

v0.16.0

This release is hopefully one of the last major tags before a more stable CertMagic 1.0. It includes a number of breaking changes (for the better, I promise) -- so please pay attention:

• ⚠️ All storage methods now require context.Context passed in. We also added it to CleanUpOwnLocks() and several other functions that end up calling Storage methods (e.g. CacheUnmanagedTLSCertificate()). Your editor, in combination with gopls (the Go language server) should be able to quickly tell you where context is missing.
• ⚠️ Storage methods now return fs.ErrNotExist if a file or key is not found, instead of certmagic.ErrNotExist, which has been removed. (The io/fs package did not exist when CertMagic was first written.)
• ⚠️ ACMEManager has been renamed to ACMEIssuer, and CertificateManager has been renamed to Manager. These renames make naming more consistent and accurate, and less confusing (since ACMEManager was not a CertificateManager, which is a new type).
• Certificate events now provide more useful, actionable information. See #150.

I have personally submitted PRs to the more popular known storage implementations as a courtesy to help deal with the breaking changes.

The nuances of the logic in preparing for DNS challenges have changed slightly, hopefully it will work in more environments.

Thanks to all who contributed! Sorry for any inconvenience with the breaking changes; that's the joy of pre-1.0 libraries. We're almost there, though. It's been 5 years and we might finally be starting to get good at things.

What's Changed

• storage: Require fs.ErrNotExist (fix #168) by @​mholt in caddyserver/certmagic#170
• Propagate context in the Storage interface methods by @​hairyhenderson in caddyserver/certmagic#155
• Fix crash because of a zero value cert in cache by @​skeetmtp in caddyserver/certmagic#177
• Always call checkDNSPropagation in DNS01Solver by @​crccw in caddyserver/certmagic#179
• Provide more detailed information in certificate events by @​francislavoie in caddyserver/certmagic#150

... (truncated)

Commits

• 2e8dd44 Upgrade a couple dependencies
• 79babff Treat empty lockfiles as stale
• 5deb7c2 Make logger values required
• 93fd493 Nil check before logging (#207)
• 55fc6a9 Avoid nil dereferencing on errors (#206)
• 9826a4c SERVFAIL should be forgivable
• 3f145a9 readme: Document events
• 2e22c6f Report issuers tried on cert_failed (fix #204)
• ab3db75 If DecisionFunc errors, log it and return currentCert
• cef8e27 Add error to cert_failed events
• 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 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]

The following labels could not be found: dependency.