The GitHub Actions job "Tests AMD" on airflow.git/fix-sbom-command has succeeded. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 6389674699fe393bfb46d561b34194a520baefe4 / Jarek Potiuk <[email protected]> Fix SBOM commands to be suitable for running in CI There were a couple of problems that prevented the SBOM generation to successfully run in our workflows: * remote_name was hard-coded to "apache" for locally pulling tags from the right remote - and we did not have that remote in CI * python parameter was set by default to "default_python_version" in CI, and what we really wanted is to have it empty to use all historical versions of python * generating SBOMs used the "ref" version of breeze rather than "current PR version" of breeze. * python version installed was the default python version that was used in the "reference" of built docs - not the "current" default version - which made it impossible to reinstall breeze to current version when old version of Python was not supported any more * When RC version SBOM was generated, it did not use RC constraints and tags so, all SBOMS were silently skipped. This is fixed by: * you can now pass remote-name as option * historical_python_versions click option now uses --python-versions and PYTHON_VERSIONS envvar and can take list of versions separated by comas - to not confuse it with regular --python option * switching temporarily to the "current-version" of breeze when generating SBOM * we are installing breeze with "current" default python version - assuming that this version will be supported by any versions of packages we want to build the documentation for * when RC version is passed as ref, we are using RC version of constraints and tags but we still produce sboms for "base" version - matching the way how documentation is done. Report URL: https://github.com/apache/airflow/actions/runs/16072696272 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
