Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented May 6, 2025

Usually release manager bumps the version of providers, but in case another provider or airflow core depends on the new version, they should be bumped together, in order to make CI and uv workspace to work together.


^ 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 airflow-core/newsfragments.

Usually release manager bumps the version of providers, but in
case another provider or airflow core depends on the new version,
they should be bumped together, in order to make CI and uv workspace
to work together.
Copy link
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was quick!

@potiuk potiuk merged commit 4728fff into apache:main May 6, 2025
47 checks passed
@potiuk potiuk deleted the fix-comment-in-provider-yaml branch May 6, 2025 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants