From: Jason Schonberg <schonm@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Jason Schonberg <schonm@gmail.com>
Subject: [meta-oe][wrynose][PATCH] nodejs: upgrade 22.22.3 -> 22.23.0
Date: Fri, 19 Jun 2026 00:35:56 -0400 [thread overview]
Message-ID: <20260619043556.1880365-1-schonm@gmail.com> (raw)
This is the June 2026 security release.
https://nodejs.org/en/blog/vulnerability/june-2026-security-releases
Changelog: https://github.com/nodejs/node/releases/tag/v22.23.0
Signed-off-by: Jason Schonberg <schonm@gmail.com>
---
.../oe-npm-cache | 0
...oe-cache-native_22.22.bb => nodejs-oe-cache-native_22.23.bb} | 0
.../nodejs/{nodejs_22.22.3.bb => nodejs_22.23.0.bb} | 2 +-
3 files changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-devtools/nodejs/{nodejs-oe-cache-22.22 => nodejs-oe-cache-22.23}/oe-npm-cache (100%)
rename meta-oe/recipes-devtools/nodejs/{nodejs-oe-cache-native_22.22.bb => nodejs-oe-cache-native_22.23.bb} (100%)
rename meta-oe/recipes-devtools/nodejs/{nodejs_22.22.3.bb => nodejs_22.23.0.bb} (99%)
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-22.22/oe-npm-cache b/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-22.23/oe-npm-cache
similarity index 100%
rename from meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-22.22/oe-npm-cache
rename to meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-22.23/oe-npm-cache
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_22.22.bb b/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_22.23.bb
similarity index 100%
rename from meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_22.22.bb
rename to meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-native_22.23.bb
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs_22.22.3.bb b/meta-oe/recipes-devtools/nodejs/nodejs_22.23.0.bb
similarity index 99%
rename from meta-oe/recipes-devtools/nodejs/nodejs_22.22.3.bb
rename to meta-oe/recipes-devtools/nodejs/nodejs_22.23.0.bb
index a13b71b762..a55a8d8940 100644
--- a/meta-oe/recipes-devtools/nodejs/nodejs_22.22.3.bb
+++ b/meta-oe/recipes-devtools/nodejs/nodejs_22.23.0.bb
@@ -39,7 +39,7 @@ SRC_URI:append:class-target = " \
SRC_URI:append:toolchain-clang:powerpc64le = " \
file://0001-ppc64-Do-not-use-mminimal-toc-with-clang.patch \
"
-SRC_URI[sha256sum] = "f3e6a578db1ab335a4a72785c1e87ad18a2cf6d2fc25747a1d741fb34af0bd0f"
+SRC_URI[sha256sum] = "3acfae100c7b855a4c76520ee0f95cadcace3f4254f16b7d4887f178fc95d4a0"
S = "${UNPACKDIR}/node-v${PV}"
--
2.43.0
reply other threads:[~2026-06-19 4:36 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=20260619043556.1880365-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