This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/plc4go/golang.org/x/net-0.26.0
in repository https://gitbox.apache.org/repos/asf/plc4x.git
discard 085d823ee3 build(deps): bump golang.org/x/net from 0.25.0 to 0.26.0 in
/plc4go
add 95a8d458ab build(deps): bump pytest from 8.2.1 to 8.2.2 in /plc4py
(#1638)
add b174f28777 build(deps): bump nodeenv from 1.9.0 to 1.9.1 in /plc4py
(#1637)
add 87cf36263e build(deps): bump golang.org/x/text from 0.15.0 to 0.16.0
in /plc4go (#1636)
add 1d1aba2d93 build(deps): bump golang.org/x/net from 0.25.0 to 0.26.0 in
/plc4go
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 (085d823ee3)
\
N -- N -- N
refs/heads/dependabot/go_modules/plc4go/golang.org/x/net-0.26.0 (1d1aba2d93)
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:
plc4py/requirements.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
