From 3c730550841c4bb5fa97457ec6d4e7ad92efa483 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Richard=20K=C3=B6rber?= <github@shredzone.org>
Date: Mon, 4 Nov 2019 00:22:47 +0100
Subject: [PATCH] Remove references to ACMEv1

---
 .github/ISSUE_TEMPLATE.md      | 7 -------
 README.md                      | 2 --
 src/site/markdown/migration.md | 5 -----
 3 files changed, 14 deletions(-)
 delete mode 100644 .github/ISSUE_TEMPLATE.md

diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
deleted file mode 100644
index 99716abb..00000000
--- a/.github/ISSUE_TEMPLATE.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<!--
-
-Thank you for submitting an issue!
-
-Please state the acme4j version you are using, so we know whether the bug is related to the ACMEv1 or ACMEv2 protocol.
-
--->
diff --git a/README.md b/README.md
index 38d3a86b..5ec6629d 100644
--- a/README.md
+++ b/README.md
@@ -8,8 +8,6 @@ This Java client helps connecting to an ACME server, and performing all necessar
 
 It is an independent open source implementation that is not affiliated with or endorsed by _Let's Encrypt_.
 
-**IMPORTANT: Starting November 1st, 2019, all _acme4j_ versions before v2.5 will not work properly any more.** Make sure to update to the latest _acme4j_ version in time. See [here](https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauthenticated-resource-gets/74380) and [here](https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430) for details. You will find help for migrating your code in the [migration guide](https://shredzone.org/maven/acme4j/migration.html).
-
 ## Features
 
 * Fully [RFC 8555](https://tools.ietf.org/html/rfc8555) compliant
diff --git a/src/site/markdown/migration.md b/src/site/markdown/migration.md
index a61c64f3..7521d0df 100644
--- a/src/site/markdown/migration.md
+++ b/src/site/markdown/migration.md
@@ -4,11 +4,6 @@ This document will help you migrate your code to the latest _acme4j_ version.
 
 <div class="alert alert-info" role="alert">
 
-**Starting on November 1st, 2019, all _acme4j_ versions before 2.5 will not work properly any more.**
-
-I recommend to update at least to this _acme4j_ version as soon as possible! _Let's Encrypt_ has [announced a sunset date for GET requests](https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauthenticated-resource-gets/74380) on November 1st, 2019. On the same day [access to the ACMEv1 servers](https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430) will be restricted.
-</div>
-
 ## Migration to Version 2.7
 
 - Note that _acme4j_ has an `Automatic-Module-Name` set in the acme-client and acme-utils modules now. If you have added _acme4j_ to your Java 9+ module dependencies, you'll need to fix your dependency declaration to `org.shredzone.acme4j` (acme-client) and `org.shredzone.acme4j.utils` (acme-utils).