fix: (source-shopify) - Update the deprecation deadline for the change the change #51037
#51602
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
bazarnov
changed the title
deprecation deadline for the change [the change](https://github.com/airbytehq/airbyte/pull/51037)deprecation deadline for the change the change #51037
aaronsteers
reviewed
Jan 16, 2025
aaronsteers
approved these changes
Jan 16, 2025
There was a problem hiding this comment.
Approving. And force-merging as discussed in the oncall thread here (internal link).
aaronsteers
deleted the
baz/baz/source-shopify/update-deprecation-deadline
branch
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
After the products graph ql stream deprecation change, the
/productsrest endpoint stopped serving the requests for the2023-07, which the last one relies on.This created the situation when the new release is available, the old data is not available but the sync keeps spinning the older version that tries to pull the old data continuously.
To solve this, we're pushing the
UpgradeDeadlineto the effective date of this PR created.How
metadata.yamlUser Impact
The customers affected should be automatically upgraded to the
2.6.1accepting the breaking change.Can this PR be safely reverted and rolled back?