Bump dehydrated to v0.7.1 #291
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Notably this includes support for asynchronous order finalization, which was tentatively scheduled to be released in April, however was postponed indefinitely: https://community.letsencrypt.org/t/enabling-asynchronous-order-finalization/193522/8 However, for a brief period between 7/13 and 7/14, I saw errors issuing certifcates looking highly similar to what was initially reported when Let's Encrypt tried the roll out of asychronous order finalization: https://community.letsencrypt.org/t/openresty-with-resty-auto-ssl-failing-with-curl-error-3/195924/1 Fixes auto-ssl#289
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notably this includes support for asynchronous order finalization, which was tentatively scheduled to be released in April, however was postponed indefinitely:
https://community.letsencrypt.org/t/enabling-asynchronous-order-finalization/193522/8
However, for a brief period between 7/13 and 7/14, I saw errors issuing certifcates looking highly similar to what was initially reported when Let's Encrypt tried the roll out of asychronous order finalization: https://community.letsencrypt.org/t/openresty-with-resty-auto-ssl-failing-with-curl-error-3/195924/1
Fixes #289