Daniel McCarney

> tomorrow is the release date for LE wildcard support. @rastographics FYI, the release date [has been delayed](https://community.letsencrypt.org/t/acmev2-and-wildcard-launch-delay/53654).

This pulls in an update to the Prometheus golang client library with breaking API changes: https://github.com/letsencrypt/boulder/issues/4588 I think it makes sense to do an upgrade to that library separately ahead...

Based on how #4605 went I think this task needs to be broken up into many smaller update PRs. Updating ct-go bumps the following deps: ``` - github.com/go-sql-driver/mysql v1.4.1-0.20191114115753-b4242bab7dc5 +...

I've put up PRs for the first four of the eight dependencies (doing the easier ones first). I'll open PRs for the other four once the outstanding PRs are merged...

Three more update PRs out for review. Calling it quits for today. I'll pick up the mysql and ct-go updates in the next week.

> Afterwards we can update ct-go. We should use a commit newer than fefcf95 to ensure we don't pull in unnecessary golangci-lint deps. This isn't accurate anymore. Per @jsha we...

> According to the spec, the server may return a Retry-After header containing a value in seconds after which one may retry the same operation. That's true, but I wanted...

@jeromegn I'm hopeful we can add it one day. I suspect it will be something we would evaluate as part of the ["v2" implementation](https://letsencrypt.org/2017/06/14/acme-v2-api.html) for Jan 2018. Apologies for being...

@parkr The `Retry-After` header is still unimplemented in Boulder. Are you targeting a different ACME server than one run by Let's Encrypt?

> Do we know if this has been implemented by boulder when using ACME v2? Boulder doesn't implement `Retry-After` for V1 or V2 at the present time.