From f92ec4889a9faaaeb74a4b14da50c87ca65a0e89 Mon Sep 17 00:00:00 2001
From: Mike Alfare <13974384+mikealfare@users.noreply.github.com>
Date: Wed, 20 Mar 2024 13:38:29 -0400
Subject: [PATCH] [Bug] Python driver 2.0.918 causes SSL error. Need to revert
 back to 2.0.917 (#731)

* cap redshift-connector at 2.0.917 to avoid ssl issue in 2.0.918

* changie
---
 .changes/unreleased/Fixes-20240317-113447.yaml | 6 ++++++
 setup.py                                       | 2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)
 create mode 100644 .changes/unreleased/Fixes-20240317-113447.yaml

diff --git a/.changes/unreleased/Fixes-20240317-113447.yaml b/.changes/unreleased/Fixes-20240317-113447.yaml
new file mode 100644
index 000000000..4338fc95b
--- /dev/null
+++ b/.changes/unreleased/Fixes-20240317-113447.yaml
@@ -0,0 +1,6 @@
+kind: Fixes
+body: Pin `redshift-connector` to <2.0.918 to avoid SSL error introduced in 2.0.918
+time: 2024-03-17T11:34:47.873169-04:00
+custom:
+  Author: mikealfare
+  Issue: "730"
diff --git a/setup.py b/setup.py
index beffa3348..234e7c97d 100644
--- a/setup.py
+++ b/setup.py
@@ -64,7 +64,7 @@ def _plugin_version_trim() -> str:
         f"dbt-postgres~={_plugin_version_trim()}",
         # dbt-redshift depends deeply on this package. it does not follow SemVer, therefore there have been breaking changes in previous patch releases
         # Pin to the patch or minor version, and bump in each new minor version of dbt-redshift.
-        "redshift-connector<=2.0.918, >=2.0.913, !=2.0.914",
+        "redshift-connector<2.0.918,>=2.0.913,!=2.0.914",
         # installed via dbt-core but referenced directly; don't pin to avoid version conflicts with dbt-core
         "sqlparse>=0.2.3,<0.5",
         "agate",