From: Antonin Godard <antonin.godard@bootlin.com>
To: openembedded-core@lists.openembedded.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Antonin Godard <antonin.godard@bootlin.com>
Subject: [PATCH] python3-pygments: update 2.20.0 -> 2.21.0
Date: Mon, 17 Aug 2026 12:13:20 +0200 [thread overview]
Message-ID: <20260817-update-pygments-v1-1-da836eab9640@bootlin.com> (raw)
One notable change from this update is the addition of a Bitbake lexer,
which will allow us to do proper Bitbake syntax coloring in our
documentation.
Full list of changes:
https://github.com/pygments/pygments/releases/tag/2.21.0
Tested using this version for the documentation with our
buildtools-docs-tarball recipe.
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
.../python/{python3-pygments_2.20.0.bb => python3-pygments_2.21.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-pygments_2.20.0.bb b/meta/recipes-devtools/python/python3-pygments_2.21.0.bb
similarity index 80%
rename from meta/recipes-devtools/python/python3-pygments_2.20.0.bb
rename to meta/recipes-devtools/python/python3-pygments_2.21.0.bb
index abe6205292..044014b134 100644
--- a/meta/recipes-devtools/python/python3-pygments_2.20.0.bb
+++ b/meta/recipes-devtools/python/python3-pygments_2.21.0.bb
@@ -5,7 +5,7 @@ LICENSE = "BSD-2-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=36a13c90514e2899f1eba7f41c3ee592"
inherit python_hatchling
-SRC_URI[sha256sum] = "6757cd03768053ff99f3039c1a36d6c0aa0b263438fcab17520b30a303a82b5f"
+SRC_URI[sha256sum] = "610ca751c9bc2492b38eb9a38a7fbc93edbbb2d7182edaf34e66ae493dee5c8c"
inherit pypi
---
base-commit: 07a342aa80c7349dd014f743a695a5e006add8df
change-id: 20260817-update-pygments-1b579985f5c1
reply other threads:[~2026-08-17 10:13 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-all 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=20260817-update-pygments-v1-1-da836eab9640@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thomas.petazzoni@bootlin.com \
/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