Missing oras module error in check_versions_downgrade

Summary

Missing oras module error in check_versions_downgrade after !5633 (merged)

$ .gitlab/ci/scripts/check_versions_downgrade.sh
Current branch is: 3413-backport-1-6-doc-have-units-description-md-include-appversion-for-helm-charts and target branch is release-1.6
Current version: 1.6, Next release branch: release-1.7
Next Sylva branch release-1.7 not found, using 'main': main
From https://gitlab.com/sylva-projects/sylva-core
 * branch            3413-backport-1-6-doc-have-units-description-md-include-appversion-for-helm-charts -> FETCH_HEAD
 * [new branch]      3413-backport-1-6-doc-have-units-description-md-include-appversion-for-helm-charts -> origin/3413-backport-1-6-doc-have-units-description-md-include-appversion-for-helm-charts
Traceback (most recent call last):
  File "/builds/sylva-projects/sylva-core/./tools/generate_units_documentation.py", line 26, in <module>
    from oras.client import OrasClient
ModuleNotFoundError: No module named 'oras'

Observed when working on !6665 (merged) .

Steps to reproduce

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Possible fixes

Edited Jan 23, 2026 by Alex Ghita
Assignee Loading
Time tracking Loading