-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
conectors-qa: verify connector breaking changes are at least 7 days ahead #35387
conectors-qa: verify connector breaking changes are at least 7 days ahead #35387
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
e418127
to
8f55503
Compare
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 think you have to rebase your branch on master
now that I merged in the package. Please bump the package version and add a changelog entry in the README.
I like this check addition but I'm concerned that this check will fail if we periodically run it on master
.
This package is able to create a global JSON reports of all our connectors QA check result. The idea was to periodically generate it to spot which connector is not passing the QA checks.
I think we should make this check fetch the OSS registry, if the current connector version is in it we can skip this check as it'd mean the connector version is already released.
airbyte-ci/connectors/connectors_qa/connectors_qa/checks/metadata.py
Outdated
Show resolved
Hide resolved
airbyte-ci/connectors/connectors_qa/connectors_qa/checks/metadata.py
Outdated
Show resolved
Hide resolved
airbyte-ci/connectors/connectors_qa/connectors_qa/checks/metadata.py
Outdated
Show resolved
Hide resolved
airbyte-ci/connectors/connectors_qa/connectors_qa/checks/metadata.py
Outdated
Show resolved
Hide resolved
@alafanechere yep, the main goal of this is to run on pull requests, not on main. I would prefer to not overcomplicate and configure running only on pull requests explicitly, at least for this check. Is that an option? Also, holy crap, I learned a few things — thank you for the review! 👏🏼 |
d253539
to
c679df0
Compare
@alafanechere alright, I've cleaned up the things you pointed out (thank you!) but have not added tests yet. Help me out — how do we make this check optional on nightly runs? @katmarkham really wanted that one ;) |
@alafanechere boop. I think aside from borked formatting I should be close! Want to pair tomorrow on both of my PRs? |
c679df0
to
533316d
Compare
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @natikgadzhi and the rest of your teammates on Graphite |
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.
Seems there's an angry unit test and I'm not sure why, but otherwise I'm happy with the way you added the check guard, @alafanechere.
I can take a look in a bit and get this over the finish line if you wish.
@@ -1,6 +1,6 @@ | |||
[tool.poetry] | |||
name = "connectors-qa" | |||
version = "1.1.0" | |||
version = "1.2.0" |
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.
Thank you <3
@@ -43,6 +43,11 @@ Connectors must have a language tag in their metadata. It must be set in the `ta | |||
*Applies to the following connector languages: python, low-code* | |||
|
|||
Python connectors must have a CDK tag in their metadata. It must be set in the `tags` field in metadata.yaml. The values can be `cdk:low-code`, `cdk:python`, or `cdk:file`. | |||
### Breaking change deadline should be a week in the future |
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.
Thank you for running the generator!
8deb9a3
to
4da8624
Compare
533316d
to
acfcd3c
Compare
acfcd3c
to
ad50e1e
Compare
Summary
This PR adds a check to
connectors-qa
by @alafanechere to verify that if a connector has a breaking change defined in it's most recent version, than it'supgradeDeadline
is at least 7 days away.Closes airbytehq/airbyte-internal-issues#6294
That's assuming that we actually run connectors-qa on all connectors, including certified 🙃
Impact
TODOs