amoghrajesh commented on code in PR #33144: URL: https://github.com/apache/airflow/pull/33144#discussion_r1285910200
########## BREEZE.rst: ########## @@ -2106,13 +2106,30 @@ Those are all available flags of ``generate-constraints`` command: In case someone modifies setup.py, the scheduled CI Tests automatically upgrades and pushes changes to the constraint files, however you can also perform test run of this locally using -the procedure described in `Refreshing CI Cache <dev/REFRESHING_CI_CACHE.md#manually-generating-constraint-files>`_ +the procedure described in the +`Manually generating image cache and constraints <dev/MANUALLY_GENERATING_IMAGE_CACHE_AND_CONSTRAINTS.md>`_ which utilises multiple processors on your local machine to generate such constraints faster. This bumps the constraint files to latest versions and stores hash of setup.py. The generated constraint and setup.py hash files are stored in the ``files`` folder and while generating the constraints diff of changes vs the previous constraint files is printed. +Updating constraints +"""""""""""""""""""" + +Sometimes (very rarely) we might want to update individual packages in constraints that we generated and +tagged already in the past. This can be done using ``breeze release-management update-constraints`` command. + +Those are all available flags of ``update-constraints`` command: Review Comment: Small nit that i came across while reading the PR. Feel free to ignore it :) -- 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]
