-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source LinkedIn Ads - Update CDK #51041
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
airbyte-integrations/connectors/source-linkedin-ads/pyproject.toml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved
@@ -1,11 +1,13 @@ | |||
# This file is automatically @generated by Poetry 1.6.1 and should not be changed by hand. | |||
# This file is automatically @generated by Poetry 2.0.0 and should not be changed by hand. | |||
|
|||
[[package]] | |||
name = "airbyte-cdk" | |||
version = "6.12.1.dev0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like it's still using the dev version of airbyte-cdk
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did run poetry lock after the cdk version change, I will take another look at this
What
This (5.1.0-rc.2) was created to upgrade the CDK because it was discovered that:
5.1.0-rc.1 PR: #48863
Was using a dev version of the CDK here.
This should have changed the CDK to a production version but for some reason the lock file was not updated. Due to this another PR was made here: #51524
However there were some failing acceptance test. To prevent blocking users from fixes already implemented, the RC rollouts were cancelled and a copy of the version created in 5.1.0-rc.1 PR was manually merged in:
Manual 5.1.0 promotion PR: #51550
How
Review guide
User Impact
Can this PR be safely reverted and rolled back?