-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Exclude yarn.lock from the whl file #16580
Conversation
cc: @uranusjr |
Tested it:
then
|
Note - The breeze command makes sure to have all the build deps installed and makes sure to cleanup of everything so that it's always reproducible. Highly recommend. |
cc: @uranusjr |
Don't close a PR and re-open a new one please -- just leave a comment. |
Ah ok. I thought its already been done before with that PR :) |
BTW. This one will need a fix in prod image building as well - I will provide the right fix in a moment |
Currently the airflow wheel is built with the yarn.lock which is not actually used by the airflow itself. Having this file in the docker image causes the clair and trivy scanners to fail. The yarn.lock however is needed in sdist package that's why it should not be excluded via MANIFEST.in Alse asset compilation only happens when Airflow is installed from sources. When Airflow is installed from packages, the assets are already compiled-in during package building.
705948d
to
b1c9bda
Compare
Sorry again for closing the original PR, I just pushed my stuff after testing without too much thinking of it, and then closed the other one. Anyway I also added fix that should fix the PROD image building. Turned out the "asset compilation" step was not really needed (and not possible when we missed yarn.lock) when Airflow is installed from packages. Now wo only compile the assets when airflow in prod image is built from sources (which is basically only when we use breeze to build it to test the latest version). |
I mixed sdist with source package. My bad |
Currently the airflow wheel is built with the yarn.lock which
is not actually used by the airflow itself. Having this file in the
docker image causes the clair and trivy scanners to fail.
The yarn.lock however is needed in sdist package that's why it should
not be excluded via MANIFEST.in
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.