SNOW-1308650: revert breaking change and release a newer version #1916
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sfc-gh-aalam
approved these changes
Apr 8, 2024
sfc-gh-jrose
approved these changes
Apr 8, 2024
…se-snowflake-connector-python-3-8-1-without-the-breaking-change
sfc-gh-aling
deleted the
SNOW-1308650-re-release-snowflake-connector-python-3-8-1-without-the-breaking-change
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please answer these questions before submitting your pull requests. Thanks!
What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes SNOW-1308650
Fill out the following pre-review checklist:
Please describe how your code solves the related issue.
Please write a short description of how your code change solves the related issue.
revert the code change introduced in PR: #1899
this is a breaking change, we have yanked the release v3.8.0.
release a newer version 3.8.1 reverting the breaking change.
for the change itself, we should do the bug fix in the future in a non-breaking way.