Install ATEX version 0.11 specifically in the Github workflow #14292
+2
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jiri Jaburek <comps@nomail.dom>
comps
changed the title
ATEX Test ResultsTest artifacts have been submitted to Testing Farm. Results: View Test Results This comment was automatically generated by the ATEX workflow. |
Mab879
approved these changes
Jan 9, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Always install the 0.11 ATEX release from PyPI, for now.
Rationale:
ATEX is still under development and API breakages will happen (at least 1-2 are planned, there might be more unplanned) before the 1.0 version is released.
Using a fixed version in the workflow allows us to update the API-using code in the same PR that bumps the version - the main benefit is that other PRs are not impacted by any ATEX-related changes because they either
so they don't need to worry about rebasing.
I know @ggbecker wanted the version-less approach, but I still think it would be more trouble than it's worth at this stage of ATEX development.