From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>
Subject: [PATCH v3 1/1] pip: bump antlr4-python3-runtime from 4.7.1 to 4.11.1
Date: Tue, 29 Nov 2022 12:07:47 -0500 [thread overview]
Message-ID: <20221129170747.2080-1-mikuback@linux.microsoft.com> (raw)
From: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps [antlr4-python3-runtime](http://www.antlr.org)
from 4.7.1 to 4.11.1.
Original automated dependabot PR:
https://github.com/tianocore/edk2/pull/3672
For reference: antlr4 release history:
https://github.com/antlr/antlr4/releases
For reference: antlr4 4.7.1 to 4.11.1 release delta:
https://github.com/antlr/antlr4/compare/4.7.1...4.11.1
Original 4.7.1 release info (December 9, 2017):
https://github.com/antlr/antlr4/releases/tag/4.7.1
Current 4.11.1 release info (September 4, 2022):
https://github.com/antlr/antlr4/releases/tag/4.11.1
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Co-authored-by: dependabot[bot] <support@github.com>
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
---
Notes:
Note: The first patch was sent as "v2" so
there is not "v1" version for this patch.
v3 changes:
- Add antlr4 release info in commit message
pip-requirements.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pip-requirements.txt b/pip-requirements.txt
index be8c7a1c37e6..597cb674c573 100644
--- a/pip-requirements.txt
+++ b/pip-requirements.txt
@@ -15,4 +15,4 @@
edk2-pytool-library==0.12.1
edk2-pytool-extensions~=0.20.0
edk2-basetools==0.1.39
-antlr4-python3-runtime==4.7.1
+antlr4-python3-runtime==4.11.1
--
2.28.0.windows.1
reply other threads:[~2022-11-29 17:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221129170747.2080-1-mikuback@linux.microsoft.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox