Bump version to 1.3.0 #1004
Merged
Bump version to 1.3.0 #1004
Conversation
This file contains 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
added 2 commits
November 19, 2019 11:13
The script was a little confusing when dependencies needed to be updated, because it wasn't clear how exactly to update the assets/license_finder.txt file With these changes the file is updated directly and the `git diff` is used to determine if there is a difference The CONTRIBUTING directions for updating the license info have also been updated to be clearer. Even so, it is clear that further improvements can be made to make this process even more seamless (and in particular, automatable).
izgeri
force-pushed
the
bump-version-1.3.0
branch
from
e27a390 to
c7e71ec
Compare
izgeri
force-pushed
the
bump-version-1.3.0
branch
from
c7e71ec to
c9ce9cc
Compare
sgnn7
approved these changes
Nov 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do (include background context, if relevant)?
Bumps the version to 1.3.0 to include new automated tests and the alpha MSSQL connector, and a bug fix for MySQL to ensure the
sslmodeconfig has appropriate defaults.What is the status of the manual tests?
Have you run the following manual tests to verify existing functionality continues to function as expected?
Links to open issues for related documentation (in READMEs, docs, etc)
#1003 is open for adding a README to the alpha MSSQL connector, since there is currently no documentation available for how to try it out