Skip to content

Track latest PyPI releases of tango-pyaml/pyaml-cs-oa in dt4acc CI - #417

Merged
gupichon merged 3 commits into
mainfrom
416-buxfix-dt4acc-integrationyml-pins-tango-pyamlpyaml-cs-oa-to-fixed-git-refs-instead-of-tracking-the-latest-pypi-release
Sep 14, 2026
Merged

gupichon merged 3 commits into
mainfrom
416-buxfix-dt4acc-integrationyml-pins-tango-pyamlpyaml-cs-oa-to-fixed-git-refs-instead-of-tracking-the-latest-pypi-release

Conversation

@gupichon

Copy link
Copy Markdown
Member

Install these companion packages unpinned from PyPI instead of fixed git refs (commit hash / tag), so the dt4acc smoke test stays current with newly published releases instead of testing a stale snapshot.

Fixes #416

Install these companion packages unpinned from PyPI instead of fixed git refs (commit hash / tag), so the dt4acc smoke test stays current with newly published releases instead of testing a stale snapshot.

Fixes #416
JeanLucPons
JeanLucPons previously approved these changes Sep 14, 2026
@gupichon

Copy link
Copy Markdown
Member Author

@TeresiaOlsson, @JeanLucPons, what do you prefer? Should I point it to:

  1. The latest release on PyPI, which means downgrading the BESSY II example to make it work.
  2. The latest on GitHub, but this prevents users from having an example that actually works with the PyPI release (as is currently the case).

Personally, I lean toward option 1, but I’m happy to go with the consensus. I don't have a strong opinion either way.

@gupichon

Copy link
Copy Markdown
Member Author

@JeanLucPons, thanks for the review! Just a heads-up: I'll need to update the BESSY II example to match the PyPI version, which will dismiss your review.

@JeanLucPons

JeanLucPons commented Sep 14, 2026

Copy link
Copy Markdown
Member

I agree with point 1

Install these companion packages unpinned from PyPI instead of fixed git refs (commit hash / tag), so the dt4acc smoke test stays current with newly published releases instead of testing a stale snapshot.

Fixes #416
@TeresiaOlsson

Copy link
Copy Markdown
Member

I agree with point 1

Me too. It feels more robust to me to always test against latest release. Then at least the tests runs against a stable source.

@gubaidulinvadim
gubaidulinvadim self-requested a review September 14, 2026 14:08
@gubaidulinvadim
gubaidulinvadim dismissed their stale review September 14, 2026 14:09

Why is the smoke test still failling?

Install these companion packages unpinned from PyPI instead of fixed git refs (commit hash / tag), so the dt4acc smoke test stays current with newly published releases instead of testing a stale snapshot.

Fixes #416
@gupichon

Copy link
Copy Markdown
Member Author

@gubaidulinvadim, the test is fine now.

@gupichon
gupichon merged commit b5bce55 into main Sep 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BuxFix: dt4acc-integration.yml pins tango-pyaml/pyaml-cs-oa to fixed git refs instead of tracking the latest PyPI release

5 participants