Skip to content

Prepare 2.4 release #324

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jku merged 1 commit into from
Nov 3, 2025
+1 −1
Merged

Prepare 2.4 release #324

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tuf_conformance/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import pytest

__version__ = "2.3.0"
__version__ = "2.4.0"
Copy link
Member Author

@jku jku Nov 3, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we could in fact remove this version number and use tags only -- this never gets published to pypi so bumping the number is not really that useful 🤷

That said, we could embed this number in the conformance result json that is published so the report could show which version of the test suite the client is using... so maybe it is useful

Copy link
Contributor

@rdimitrov rdimitrov Nov 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's actually a good idea 👍


# register pytest asserts before the imports happen in conftest.py
pytest.register_assert_rewrite("tuf_conformance._internal.client_runner")
Loading