Fix release process issues after going through 2025-12-09 release #59261
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
kaxil
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
Member
Author
potiuk
commented
Dec 10, 2025
dev/breeze/src/airflow_breeze/prepare_providers/provider_documentation.py
Show resolved
Hide resolved
potiuk
commented
Dec 10, 2025
potiuk
commented
Dec 10, 2025
There were a few issues found during the process of relasing providers 2025-12-09: * the comment `# use next version` is likely to have one or more spaces separating from the requirement and some following characters the extra space is now stripped and everything after the comment is removed. * updating next version of providers leads to changing provider dependencies, and the .json locally stored where we keep the deps should be updated * index.rst for providers were not updated in prek hook even if provider dependencies changed
potiuk
force-pushed
the
fix-release-provider-issues-2025-12-09
branch
from
6c1786f to
44fcd21
Compare
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 98fee1e v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
potiuk
added a commit
that referenced
this pull request
Dec 28, 2025
…9261) There were a few issues found during the process of relasing providers 2025-12-09: * the comment `# use next version` is likely to have one or more spaces separating from the requirement and some following characters the extra space is now stripped and everything after the comment is removed. * updating next version of providers leads to changing provider dependencies, and the .json locally stored where we keep the deps should be updated * index.rst for providers were not updated in prek hook even if provider dependencies changed
54 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There were a few issues found during the process of relasing providers 2025-12-09:
the comment
# use next versionis likely to have one or more spaces separating from the requirement and some following characters the extra space is now stripped and everything after the comment is removed.updating next version of providers leads to changing provider dependencies, and the .json locally stored where we keep the deps should be updated
index.rst for providers were not updated in prek hook even if provider dependencies changed
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.