[GH] (airflow/separate-release-image-workflows-per-python): Workflow run "Release PROD images" failed!
The GitHub Actions job "Release PROD images" on airflow.git/separate-release-image-workflows-per-python has failed. Run started by GitHub user potiuk (triggered by potiuk). Head commit for run: 02ee73cf4ccd278f4a0aa0091e998b5ec4e99351 / Jarek Potiuk Split release image into per-python independent matrix of workflows The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting. Report URL: https://github.com/apache/airflow/actions/runs/14890430905 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
[GH] (airflow/separate-release-image-workflows-per-python): Workflow run "Release PROD images" failed!
The GitHub Actions job "Release PROD images" on airflow.git/separate-release-image-workflows-per-python has failed. Run started by GitHub user potiuk (triggered by potiuk). Head commit for run: 4b65f1a1452bb0080a8b95a87d935b3d0085ced2 / Jarek Potiuk Split release image into per-python independent matrix of workflows The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting. Report URL: https://github.com/apache/airflow/actions/runs/14889915650 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
[GH] (airflow/separate-release-image-workflows-per-python): Workflow run "Release PROD images" failed!
The GitHub Actions job "Release PROD images" on airflow.git/separate-release-image-workflows-per-python has failed. Run started by GitHub user potiuk (triggered by potiuk). Head commit for run: ea600b249444e9a56237eec60020ce6959f97b8a / Jarek Potiuk Split release image into per-python independent matrix of workflows The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting. Report URL: https://github.com/apache/airflow/actions/runs/14887854045 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
[GH] (airflow/separate-release-image-workflows-per-python): Workflow run "Release PROD images" failed!
The GitHub Actions job "Release PROD images" on airflow.git/separate-release-image-workflows-per-python has failed. Run started by GitHub user potiuk (triggered by potiuk). Head commit for run: fa28ebcd9cd18a4173a880f6eba7cd605173be2a / Jarek Potiuk Split release image into per-python independent matrix of workflows The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting. Report URL: https://github.com/apache/airflow/actions/runs/14887799744 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
[GH] (airflow/separate-release-image-workflows-per-python): Workflow run "Release PROD images" failed!
The GitHub Actions job "Release PROD images" on airflow.git/separate-release-image-workflows-per-python has failed. Run started by GitHub user potiuk (triggered by potiuk). Head commit for run: 0ee6c82c9158e8982981733e09ee990450fc3af9 / Jarek Potiuk Split release image into per-python independent matrix of workflows The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting. Report URL: https://github.com/apache/airflow/actions/runs/14887422066 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
[GH] (airflow/separate-release-image-workflows-per-python): Workflow run "Release PROD images" failed!
The GitHub Actions job "Release PROD images" on airflow.git/separate-release-image-workflows-per-python has failed. Run started by GitHub user potiuk (triggered by potiuk). Head commit for run: 66248c51ef54ace8d4b376619372e02ff0620487 / Jarek Potiuk Split release image into per-python independent matrix of workflows The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run. Report URL: https://github.com/apache/airflow/actions/runs/14887254394 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
[GH] (airflow/separate-release-image-workflows-per-python): Workflow run "Release PROD images" failed!
The GitHub Actions job "Release PROD images" on airflow.git/separate-release-image-workflows-per-python has failed. Run started by GitHub user potiuk (triggered by potiuk). Head commit for run: e1eab9c1d3e8c348377b536ec7790d4ab0a16269 / Jarek Potiuk Split release image into per-python independent matrix of workflows The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run. Report URL: https://github.com/apache/airflow/actions/runs/14886912159 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
[GH] (airflow/separate-release-image-workflows-per-python): Workflow run "Release PROD images" failed!
The GitHub Actions job "Release PROD images" on airflow.git/separate-release-image-workflows-per-python has failed. Run started by GitHub user potiuk (triggered by potiuk). Head commit for run: 66248c51ef54ace8d4b376619372e02ff0620487 / Jarek Potiuk Split release image into per-python independent matrix of workflows The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run. Report URL: https://github.com/apache/airflow/actions/runs/14887254394 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
[GH] (airflow/separate-release-image-workflows-per-python): Workflow run "Release PROD images" failed!
The GitHub Actions job "Release PROD images" on airflow.git/separate-release-image-workflows-per-python has failed. Run started by GitHub user potiuk (triggered by potiuk). Head commit for run: e1eab9c1d3e8c348377b536ec7790d4ab0a16269 / Jarek Potiuk Split release image into per-python independent matrix of workflows The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run. Report URL: https://github.com/apache/airflow/actions/runs/14882519484 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
