-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Prepare ad-hoc RC2 providers release 2026-01-17 #60706
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
Prepare ad-hoc RC2 providers release 2026-01-17 #60706
Conversation
e9a33df to
85044f7
Compare
shahar1
left a comment
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.
Is it still possible at this stage to include additional PRs in this release without going RC3?
If so, I'll be happy if this one will be included: #60701
Yes. Will add it. |
85044f7 to
1aac09b
Compare
1aac09b to
f549a54
Compare
|
Closing/reopening to force re-build |
82ea439 to
50161d5
Compare
Co-authored-by: Elad Kalif <45845474+eladkal@users.noreply.github.com>
50161d5 to
51c836d
Compare
|
FYI will make the next steps in cutting ad-hoc by tomorrow morning. |
* Prepare ad-hoc RC2 providers release 2026-01-17 * Add fix PR 60701 * Add fix PR 60701 * revert back to version 19.4.0 and move changelogs for breaking changes to 19.0.0 * Apply suggestion from @eladkal Co-authored-by: Elad Kalif <45845474+eladkal@users.noreply.github.com> * Adding cncf.kubernetes to ad-hoc * Revise changelog for Google --------- Co-authored-by: Elad Kalif <45845474+eladkal@users.noreply.github.com>
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.