Manually bump destination-mssql version #12291
Merged
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
github-actions
bot
added
area/connectors
grishick
force-pushed
the
greg/bump-destination-mssql-version
branch
from
8c04361
to
eb404b7
Compare
alafanechere
approved these changes
Apr 26, 2022
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
Following up on #11514
destination-mssql connector image with version 0.1.17 is already pushed to Dockerhub:
https://hub.docker.com/layers/destination-mssql/airbyte/destination-mssql/latest/images/sha256-63cde8db1821095c8e056ebdec2ff123ae9415d7408df9083ff3ef06e96c9b7c?context=explore
In this PR:
Update destination-mssql version to 0.1.17 in Dockerfile, docs, and seed config