-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Introducing --latest for generate-issue-content-core command #38250
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
Conversation
|
Can you please close and re-open the PR from the |
|
@potiuk I just did that, lets see the run |
|
The checks look fine here @potiuk. |
We can use |
Right, OR i can use the --max-count too. |
|
Yep. |
|
@potiuk thanks, its much better now! |
dev/breeze/src/airflow_breeze/commands/release_management_commands.py
Outdated
Show resolved
Hide resolved
|
@potiuk here is the output with the latest changes. Looks nice now! |
|
@potiuk finally was able to get this green. Could you take another look? |
|
🎉 |



Follow ups to #38062, there should be mechanisms to find the latest airflow versions released to integrate seamlessly with the ci. Integrating --latest, that gets the latest version of airflow from https://pypi.org/pypi/apache-airflow/json, consumed VERSION env variable and falls back in case not set graciously.
Example:
^ 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 newsfragments.