This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch jbilleter/python3.14
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard 576635339 Add support for Python 3.14
discard fd4223418 ci: Update cibuildwheel to 3.1.4
discard e3b93c3e3 ci: Update Ubuntu images from 22.04 to 24.04
add bf4e697d5 ci: Update images
add a35d0bb0d tests/integration/project/elements/recc/recc.bst: Update
recc to 1.3.39
add 0dc32cf36 Merge pull request #2070 from
apache/jbilleter/update-buildbox
add e6c8e14ef ci: Update Ubuntu images from 22.04 to 24.04
add 303a4b926 ci: Update cibuildwheel to 3.1.4
add 831f9bddf Add support for Python 3.14
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 (576635339)
\
N -- N -- N refs/heads/jbilleter/python3.14 (831f9bddf)
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:
.github/common.env | 2 +-
tests/integration/project/elements/recc/recc.bst | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
