OAuth 2 release note #52613
Merged
OAuth 2 release note #52613
+18
−0
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
the
area/documentation
marcosmarxm
approved these changes
Jan 29, 2025
bnchrch
approved these changes
Jan 31, 2025
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
Adds a release note for OAuth flow upgrades in connectors. Some users have expressed frustration that the OAuth flow had changed without warning in 1.4, and we did not appropriately notify them. Although this is a huge improvement overall, it's easy to see how someone might consider it a bug because it was an unannounced change and affected several connectors.
This one's just the release note.
A separate change will handle docs updates related to this feature. You can see that task developing here, if you like: https://github.com/airbytehq/airbyte-internal-issues/issues/11477
How
Adds content to v1.4 release notes for OAuth flow upgrades in connectors.
Review guide
/docs/release_notes/v1.4.md
User Impact
People will be able to know what's happened and when.
Can this PR be safely reverted and rolled back?