potiuk opened a new pull request, #32896:
URL: https://github.com/apache/airflow/pull/32896
So far we only applied PyPi suffix for cross-provider dependencies - i.e.
when one airflow package depended on another one released at the same time we
added "dev0" suffix to their cross-dependencies, when building them on CI so
that they can be installed together without conflicts (this is because of
decisions made with PEP-440 where version suffixes are in different namespaces
than the final versions, so it is impossible to specify "final" dependency as
minimal and have the ".dev0" satisfy it only for that single package.
With openlineage provider, we need to release it before Airflow 2.7.0 gets
released, and openlineage provider depends on Airflow 2.7.0 so we need to also
handle the situation, where OpenLineage has >= 2.7.0 for Airflow, but the
dependency that is used to resolve dependencies in CI uses 2.7.0dev0. This is
done by dynamically manipulating the dependencies in setup.py based on
VERSION_SUFFIX_FOR_PYPI variable.
This variable in CI is set to "dev0" thus all packages built have "dev0"
added as version, with this change if any package has
>= <CURRENT_AIRFLOW_VERSION> specified, it will also be extended
with the same "dev0" suffix.
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
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](https://github.com/apache/airflow/tree/main/newsfragments).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
