You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
BuxFix: dt4acc-integration.yml pins tango-pyaml/pyaml-cs-oa to fixed git refs instead of tracking the latest PyPI release #416
.github/workflows/dt4acc-integration.yml, step "Install pyAML and control-system backends", installs the two companion control-system packages from fixed git refs instead of PyPI:
pyaml-cs-oa is stuck on git tag 0.2.0, fetched via git+https://... rather than PyPI.
Problem
These pins go stale: every time a new release of tango-pyaml or pyaml-cs-oa is published, the dt4acc integration pipeline keeps testing against the old, frozen ref until someone remembers to manually bump the commit/tag in the workflow. This defeats the purpose of the smoke test, which is meant to catch incompatibilities between pyaml and the current published companion packages — not a snapshot from whenever the pin was last touched.
Expected behavior
The workflow always installs the latest published PyPI release of tango-pyaml and pyaml-cs-oa, with no fixed version/commit pin, so the integration test naturally stays current as new releases come out.
Proposal
Replace the --no-deps git install with an unpinned PyPI install:
(keep --no-deps if it's intentional here to avoid pulling unwanted transitive deps into this job; otherwise reconsider it too).
Acceptance criteria
dt4acc-integration.yml installs tango-pyaml and pyaml-cs-oa from PyPI, unpinned (always latest), with no git+https://... source and no version pin.
The dt4acc smoke test still passes against the currently published PyPI versions.
(Nice to have) if the smoke test starts failing after a new companion release, that failure is attributable to the new release — e.g. log the installed version(s) in the workflow output for easier triage.
Activity
Track latest PyPI releases of tango-pyaml/pyaml-cs-oa in dt4acc CI
Adapt the BESSY II example to follow the pypi backends versions.
Adapt the BESSY II example to follow the pypi backends versions.