-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
airbyte-ci: relax docs qa checks when sl == 0 #45360
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
58495bd
to
e656cd7
Compare
e656cd7
to
e30bdce
Compare
== f"The dockerImageTag value ({decremented_version}) can't be decremented: it should be equal to or above {current_version}." | ||
) | ||
expected_prefix = f"The dockerImageTag value ({decremented_version}) can't be decremented: it should be equal to or above" | ||
assert error_message.startswith(expected_prefix), error_message |
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.
The test expects current_version to be patch version 11 instead of 13 and currently fails in master
also. I looked into how it gets the current version, it reads it off dockerhub. Changing the assertion seemed more reasonable to me.
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.
Nice! LGTM
Thanks! #45341 is happy with these changes so I'm confident they work as expected. |
What
When developing new connectors, the QA checks related to documentation are annoying. For instance, there's no point in maintaining a changelog and being forced to adds needless friction.
How
Allow 0
sl
values in AirbyteInternal objects in metadata.yaml. For good measure, allow 0ql
values also. Make docs checks applicable only tosl >= 100
. 100 is the defaultsl
value anyway so this shouldn't break anything.Depends on #45361
Review guide
Commit by commit
User Impact
None
Can this PR be safely reverted and rolled back?