Sync with upstream go-ora
#3
Closed
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
Tener
force-pushed
the
tener/update-upstream
branch
from
766970c
to
2b4d7be
Compare
|
I don't think we can get the PR checks to pass, unfortunately. |
|
Thanks @Tener! We can drop the workflow stuff and you can release it from your branch since there is no new change (but add a date or release number to your branch so we remember where it's based off) |
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.
masterbranch was synced with upstream. Now, this PR mergesmasterintoteleportbranch and rebases our changes on top (CI,.WithTLSConfig()).The updated
.WithTLSConfig()saw large changes as upstream code was significantly restructured. I've tested the respective Teleport functionality and it continues to work after this.