diff --git a/.gitignore b/.gitignore
index 78253819b..771060650 100644
--- a/.gitignore
+++ b/.gitignore
@@ -27,4 +27,4 @@ release.properties
 **/*$py.class
 **/*.pyc
 **/.DS_Store
-system-test/domains
+**/.hugo_build.lock
diff --git a/documentation/2.0/content/developer/ReleaseProcess.md b/documentation/2.0/content/developer/ReleaseProcess.md
index eb71df9f7..5eb7b72f1 100644
--- a/documentation/2.0/content/developer/ReleaseProcess.md
+++ b/documentation/2.0/content/developer/ReleaseProcess.md
@@ -11,7 +11,7 @@ This document describes the process that should be followed to create a WebLogic
 - A local installation of WebLogic Server 12.2.1.x must be available.
 - The person running the release process must have admin privileges on the [WebLogic Deploy Tooling GitHub repo](https://github.com/oracle/weblogic-deploy-tooling) because the release process pushes to the master branch directly.
 - The person running the release process needs to create a GitHub Personal Access Token for the repository with (at least) the `repo:status`, `repo_deployment`, `public_repo`, and `security_events` privileges.
-- The person running the release needs a server added to their Maven `settings.xml` file, where the GitHub Personal Access Token is stored, as shown below.  Note that this token can either be stored in plain text or encrypted using [Maven password encryption](https://maven.apache.org/guides/mini/guide-encryption.html).
+- The person running the release process needs a server added to their Maven `settings.xml` file, where the GitHub Personal Access Token is stored, as shown below.  Note that this token can either be stored in plain text or encrypted using [Maven password encryption](https://maven.apache.org/guides/mini/guide-encryption.html).
 
 ```xml
   <servers>
@@ -22,6 +22,21 @@ This document describes the process that should be followed to create a WebLogic
   </servers>
 ```
 
+- If the machine from which the release process is being run requires a proxy server to access the Internet, the person running the release process needs an active proxy configured in their Maven `settings.xml` file.
+
+```xml
+  <proxies>
+    <proxy>
+      <active>true</active>
+      <id>my-proxy</id>
+      <protocol>http</protocol>
+      <host>proxy server DNS name</host>
+      <port>proxy server port</port>
+      <nonProxyHosts>list of DNS names/patterns separated by |</nonProxyHosts>
+    </proxy>
+  </proxies>
+```
+
 ### Software release process
 The best practice is to write the release notes that will be published to GitHub prior to starting the steps below.
 
diff --git a/github-release.xml b/github-release.xml
index b49ded3ab..b3563e675 100644
--- a/github-release.xml
+++ b/github-release.xml
@@ -40,7 +40,7 @@
                 <plugin>
                     <groupId>io.rhpatrick.mojo</groupId>
                     <artifactId>github-maven-plugin</artifactId>
-                    <version>0.6</version>
+                    <version>0.7</version>
                 </plugin>
             </plugins>
         </pluginManagement>