diff --git a/.goreleaser.yml b/.goreleaser.yml
index b2b6025e..a141da2a 100644
--- a/.goreleaser.yml
+++ b/.goreleaser.yml
@@ -43,8 +43,9 @@ checksum:
 signs:
   - artifacts: checksum
     args:
-      - "--pinentry-mode"
-      - "loopback"
+      # if you are using this is a GitHub action or some other automated pipeline, you
+      # need to pass the batch flag to indicate its not interactive.
+      - "--batch"
       - "--local-user"
       - "{{ .Env.GPG_FINGERPRINT }}" # set this environment variable for your signing key
       - "--output"
diff --git a/.ldrelease/prepare.sh b/.ldrelease/prepare.sh
index a762356f..aa93ed78 100755
--- a/.ldrelease/prepare.sh
+++ b/.ldrelease/prepare.sh
@@ -10,6 +10,12 @@ apt-get install -y --no-install-recommends \
     gnupg \
 ; \
 
+# Goreleaser does not allow us to sign our binaries with a passphrase so we have to run a dummy
+# command to get GPG to cache the passphrase. By default the cache has a TTL of 10 minutes, which is too short for our
+# builds.
+gpgconf --kill gpg-agent
+gpg-agent --daemon --default-cache-ttl 7200
+
 # Get GPG Key
 echo -e "$(cat "${LD_RELEASE_SECRETS_DIR}/gpg_private_key")" | gpg --import --batch --no-tty
 echo "hello world" > temp.txt
diff --git a/.ldrelease/publish-dry-run.sh b/.ldrelease/publish-dry-run.sh
index d3562fdd..4cdf9bc8 100755
--- a/.ldrelease/publish-dry-run.sh
+++ b/.ldrelease/publish-dry-run.sh
@@ -4,7 +4,7 @@ set -ue
 
 # Run goreleaser
 # We can't run in the build step, as project-releaser only tags the commit after the build step finishes and goreleaser pulls the tag off the most recent commit
-GPG_TTY=$(tty) GPG_FINGERPRINT=$(gpg --with-colons --list-keys | awk -F: '/^pub/ { print $5 }') GITHUB_TOKEN="$(cat "${LD_RELEASE_SECRETS_DIR}/github_token")" LD_RELEASE_ARTIFACTS_DIR="${LD_RELEASE_ARTIFACTS_DIR}" goreleaser release --debug --clean --snapshot
+GPG_FINGERPRINT=$(gpg --with-colons --list-keys | awk -F: '/^pub/ { print $5 }') GITHUB_TOKEN="$(cat "${LD_RELEASE_SECRETS_DIR}/github_token")" LD_RELEASE_ARTIFACTS_DIR="${LD_RELEASE_ARTIFACTS_DIR}" goreleaser release --clean --snapshot
 
 # Remove extra files that we don't want in our release
 rm /tmp/project-releaser/artifacts/artifacts.json
diff --git a/.ldrelease/publish.sh b/.ldrelease/publish.sh
index b708eb77..96295e32 100755
--- a/.ldrelease/publish.sh
+++ b/.ldrelease/publish.sh
@@ -4,7 +4,7 @@ set -ue
 
 # Run goreleaser
 # We can't run in the build step, as project-releaser only tags the commit after the build step finishes and goreleaser pulls the tag off the most recent commit
-GPG_TTY=$(tty) GPG_FINGERPRINT=$(gpg --with-colons --list-keys | awk -F: '/^pub/ { print $5 }') GITHUB_TOKEN="$(cat "${LD_RELEASE_SECRETS_DIR}/github_token")" goreleaser release --debug --clean --release-notes ../entry.tmp
+GPG_FINGERPRINT=$(gpg --with-colons --list-keys | awk -F: '/^pub/ { print $5 }') GITHUB_TOKEN="$(cat "${LD_RELEASE_SECRETS_DIR}/github_token")" goreleaser release --clean --release-notes ../entry.tmp
 
 # Remove extra files that we don't want in our release
 rm /tmp/project-releaser/artifacts/artifacts.json
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3ee47af6..aa20ed5a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,8 +1,3 @@
-## [2.13.0] - 2023-07-17
-FEATURES:
-
-- Adds the new `launchdarkly_team_role_mapping` resource to manage the custom roles associated with a LaunchDarkly team. This is useful if the LaunchDarkly team is created and managed externally, such as via [Okta SCIM](https://docs.launchdarkly.com/home/account-security/okta/#using-okta-to-manage-launchdarkly-teams-with-scim). If you wish to create an manage the team using Terraform, we recommend using the [`launchdarkly_team` resource](https://registry.terraform.io/providers/launchdarkly/launchdarkly/latest/docs/resources/team) instead. [#152](https://github.com/launchdarkly/terraform-provider-launchdarkly/issues/152)
-
 ## [2.12.2] - 2023-06-28
 
 BUG FIXES: