This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch juerg/python-3.13
in repository https://gitbox.apache.org/repos/asf/buildstream-plugins.git
omit 2271385 ci: Run tests also on Fedora 41
omit e4e3943 Add support for Python 3.13
omit 0d9ae1c tox.ini: Update mypy to match buildstream
omit 2d92cc3 Drop support for Python 3.8
omit 2c59b70 .github/run-ci.sh: Update last reference of Ubuntu 20.04 to
22.04
add 98d1c14 requirements: Add setuptools to test-requirements
add b58abc5 .github/run-ci.sh: Update last reference of Ubuntu 20.04 to
22.04
add 90ea905 Drop support for Python 3.8
add 06a4522 tox.ini: Update mypy to match buildstream
add 8971237 Add support for Python 3.13
add a1200c8 ci: Run tests also on Fedora 41
add 56667ba tox.ini: Test with latest BuildStream release 2.4.0
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (2271385)
\
N -- N -- N refs/heads/juerg/python-3.13 (56667ba)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
requirements/test-requirements.txt | 1 +
tox.ini | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
