-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Fix case where pip requiremet version starts with != #35645
Fix case where pip requiremet version starts with != #35645
Conversation
Github provider has package starting with `!=` and the documentation generation had a bug (for a long time) to split the package versions wrongly in this case.
@@ -39,5 +39,5 @@ | |||
"2.5.0" | |||
): | |||
raise RuntimeError( | |||
f"The package `apache-airflow-providers-github:{__version__}` requires Apache Airflow 2.5.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.
Latest template applied here as well (cc: @eladkal - this the case whe you can use --reapply-templates-only
Changes in docs were done with (after implementing the fix)
breeze release-management prepare-provider-documentation github --reapply-templates-only
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.
Look nice.
What do you think if as follow up we would migrate from custom regex to the packaging
library?
Sure. PRS are more welcome. One of the reasons why I now work on moving all the code for packaging to |
Github provider has package starting with
!=
and the documentation generation had a bug (for a long time) to split the package versions wrongly in this case.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.