From: Jason Schonberg <schonm@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Jason Schonberg <schonm@gmail.com>
Subject: [meta-oe][PATCH] nodejs: upgrade 24.21.0 -> 24.22.0
Date: Wed, 14 Oct 2026 21:51:43 -0400 [thread overview]
Message-ID: <20261015015144.504386-1-schonm@gmail.com> (raw)
Changelog: https://github.com/nodejs/node/releases/tag/v24.22.0
Signed-off-by: Jason Schonberg <schonm@gmail.com>
---
.../oe-npm-cache | 0
...oe-cache-native_24.21.bb => nodejs-oe-cache-native_24.22.bb} | 0
.../nodejs/{nodejs_24.21.0.bb => nodejs_24.22.0.bb} | 2 +-
3 files changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-devtools/nodejs/{nodejs-oe-cache-24.21 => nodejs-oe-cache-24.22}/oe-npm-cache (100%)
rename meta-oe/recipes-devtools/nodejs/{nodejs-oe-cache-native_24.21.bb => nodejs-oe-cache-native_24.22.bb} (100%)
rename meta-oe/recipes-devtools/nodejs/{nodejs_24.21.0.bb => nodejs_24.22.0.bb} (98%)
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-24.21/oe-npm-cache b/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-24.22/oe-npm-cache
similarity index 100%
rename from meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-24.21/oe-npm-cache
rename to meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-24.22/oe-npm-cache
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_24.21.bb b/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_24.22.bb
similarity index 100%
rename from meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_24.21.bb
rename to meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_24.22.bb
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs_24.21.0.bb b/meta-oe/recipes-devtools/nodejs/nodejs_24.22.0.bb
similarity index 98%
rename from meta-oe/recipes-devtools/nodejs/nodejs_24.21.0.bb
rename to meta-oe/recipes-devtools/nodejs/nodejs_24.22.0.bb
index 441a920f36..39a8563672 100644
--- a/meta-oe/recipes-devtools/nodejs/nodejs_24.21.0.bb
+++ b/meta-oe/recipes-devtools/nodejs/nodejs_24.22.0.bb
@@ -35,7 +35,7 @@ SRC_URI = "https://nodejs.org/dist/v${PV}/node-v${PV}.tar.xz \
SRC_URI:append:class-target = " \
file://0009-Using-native-binaries.patch \
"
-SRC_URI[sha256sum] = "a6f54defb6fd7c84f41dba13d61e78e9b4e0961712cf61f29715c05f5ced94fc"
+SRC_URI[sha256sum] = "41f97cff2c666f1f8293dc5f85c65e8dd605c16b43fd9febd49ede32ee1e0329"
S = "${UNPACKDIR}/node-v${PV}"
--
2.43.0
reply other threads:[~2026-10-15 1:52 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=20261015015144.504386-1-schonm@gmail.com \
--to=schonm@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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