Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Jan 15, 2024

In some circumstances, when breeze is installed in CI (when we update to newer breeze version in "build-info" workflow in old branches) breeze is not able to auto-detect sources it was installed from.

This PR changes it by passing the sources via environment variable.


^ 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.rst or {issue_number}.significant.rst, in newsfragments.

In some circumstances, when breeze is installed in CI (when we
update to newer breeze version in "build-info" workflow in old
branches) breeze is not able to auto-detect sources it was installed
from.

This PR changes it by passing the sources via environment variable.
@potiuk potiuk merged commit e8080b8 into main Jan 15, 2024
ephraimbuddy pushed a commit that referenced this pull request Jan 15, 2024
…36792)

In some circumstances, when breeze is installed in CI (when we
update to newer breeze version in "build-info" workflow in old
branches) breeze is not able to auto-detect sources it was installed
from.

This PR changes it by passing the sources via environment variable.

(cherry picked from commit e8080b8)
@Taragolis Taragolis deleted the skip-upgrade-check-when-breeze-installed branch April 3, 2024 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants