This is an automated email from the ASF dual-hosted git repository.
tvb pushed a change to branch tristan/pin-ruamel-yaml
in repository https://gitbox.apache.org/repos/asf/buildstream.git
discard 51631bdcb requirements: Updating requirements after pinning ruamel.yaml
discard 10cca2a43 requirements: Pin ujson to < 5.8
discard 6fe20f914 requirements: Pin protobuf further to < 4.22
discard e1ccc3b9a requirements: Prevent usage of pytest-datafiles >= 3.0
add 8da77f244 requirements: Pin pytest-datafiles to < 3.0
add 082660294 requirements: Pin protobuf further to < 4.22
add df6553573 requirements: Pin ujson to < 5.8
add 072861da0 requirements: Pin pylint to < 3.0
add ccb775867 requirements: Updating requirements after pinning ruamel.yaml
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 (51631bdcb)
\
N -- N -- N refs/heads/tristan/pin-ruamel-yaml (ccb775867)
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/dev-requirements.in | 2 +-
requirements/dev-requirements.txt | 6 ++++--
2 files changed, 5 insertions(+), 3 deletions(-)
