Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hard pin to 2.1.0 #843

Closed
wants to merge 1 commit into from
Closed

Conversation

VersusFacit
Copy link
Contributor

resolves #
docs dbt-labs/docs.getdbt.com/#

Problem

Solution

Checklist

  • I have read the contributing guide and understand what's expected of me
  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

@cla-bot cla-bot bot added the cla:yes label Jun 11, 2024
Copy link
Contributor

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-redshift contributing guide.

@VersusFacit VersusFacit force-pushed the adjust_redshift_connector_version branch from c1ded87 to a99d5cc Compare June 11, 2024 22:16
@VersusFacit VersusFacit added the Skip Changelog Skips GHA to check for changelog file label Jun 11, 2024
@@ -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",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should just update the upper bound to <=2.1

Copy link
Contributor Author

@VersusFacit VersusFacit Jun 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@colin-rogers-dbt I pinned it in alignment with our concern of unannounced breaking changes in the 2.1.0 family if that continues to be a real concern. This is also paired with the fact this branch is behind main. Going with a range does open us up to that.

Is that acceptable risk? Happy to make the adjustment if so

What about hard pinning this branch but using that range for main?

@VersusFacit
Copy link
Contributor Author

Closed as redundant with #844

@mikealfare mikealfare deleted the adjust_redshift_connector_version branch July 17, 2024 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla:yes Skip Changelog Skips GHA to check for changelog file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants