Commit d314d2a1 authored by Stan Hu's avatar Stan Hu

Upgrade acme-client to v2.0.5

Let's Encrypt dropped support of unauthenticated GET requests to their
staging API. This version uses POST-as-GET requests, which is the
recommended method.

This mirrors the change in Omnibus:
https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3782

Full CHANGELOG:
https://github.com/unixcharles/acme-client/blob/master/CHANGELOG.md

Diff:
https://github.com/unixcharles/acme-client/compare/v2.0.2..v2.0.5
parent 74bfdf4f
......@@ -67,7 +67,7 @@ gem 'u2f', '~> 0.2.1'
gem 'validates_hostname', '~> 1.0.6'
gem 'rubyzip', '~> 1.3.0', require: 'zip'
# GitLab Pages letsencrypt support
gem 'acme-client', '~> 2.0.2'
gem 'acme-client', '~> 2.0.5'
# Browser detection
gem 'browser', '~> 2.5'
......
......@@ -4,7 +4,7 @@ GEM
RedCloth (4.3.2)
abstract_type (0.0.7)
ace-rails-ap (4.1.2)
acme-client (2.0.2)
acme-client (2.0.5)
faraday (~> 0.9, >= 0.9.1)
actioncable (5.2.3)
actionpack (= 5.2.3)
......@@ -1131,7 +1131,7 @@ PLATFORMS
DEPENDENCIES
RedCloth (~> 4.3.2)
ace-rails-ap (~> 4.1.0)
acme-client (~> 2.0.2)
acme-client (~> 2.0.5)
activerecord-explain-analyze (~> 0.1)
acts-as-taggable-on (~> 6.0)
addressable (~> 2.7)
......
---
title: Upgrade acme-client to v2.0.5
merge_request: 23498
author:
type: other
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment