potiuk opened a new pull request, #72806:
URL: https://github.com/apache/airflow/pull/72806
Breeze was installed by resolving dev/breeze/pyproject.toml against the
package index on every fresh environment — `uvx --from ./dev/breeze` in the
shim, `uv tool install --editable ./dev/breeze` in CI. Neither reads
dev/breeze/uv.lock, and neither applies the `[tool.uv] exclude-newer` buffer
declared beside it, which governs project operations only. The committed lock
recorded nothing, so an upstream release could change what breeze runs with no
commit in this repository.
click 8.5.0 showed the cost. It added a `help` field to the argument info
dict breeze hashes to detect command drift, so within the hour of its release
every CI job resolved it, every command taking a positional argument hashed
differently from its committed value, and static checks went red on every open
PR regardless of what it touched. The lock said click 8.4.2 throughout.
The command-output files move back to the versions the lock produces; the
next lock upgrade regenerates them together with the dependency bump that
causes them. (cherry picked from commit
b42de709745ecc8105f4781915a875fb037aa4ae)
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
https://chris.beams.io/posts/git-commit/
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.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
