From: KeepBotting <KeepBotting@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nodejs: update to 22.12.0
Date: Wed, 08 Jan 2025 01:19:28 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53887@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
There is a new pull request by KeepBotting against master on the void-packages repository
https://github.com/KeepBotting/void-packages node22
https://github.com/void-linux/void-packages/pull/53887
nodejs: update to 22.12.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
- I was able to compile & run this project: https://github.com/2004Scape/Server but I'm unsure how extensive of a test this constitutes
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/53887.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-node22-53887.patch --]
[-- Type: text/x-diff, Size: 1098 bytes --]
From a194e1cdad860d27945bbc23b83f552bf3153c6c Mon Sep 17 00:00:00 2001
From: branon <branon@branon.me>
Date: Tue, 7 Jan 2025 19:16:32 -0500
Subject: [PATCH] nodejs: update to 22.12.0
---
srcpkgs/nodejs/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/nodejs/template b/srcpkgs/nodejs/template
index 08ac9829f70384..c5e3dc6ce665e7 100644
--- a/srcpkgs/nodejs/template
+++ b/srcpkgs/nodejs/template
@@ -1,6 +1,6 @@
# Template file for 'nodejs'
pkgname=nodejs
-version=20.16.0
+version=22.12.0
revision=1
hostmakedepends="which pkg-config python3-setuptools"
_make_depends="zlib-devel \
@@ -18,7 +18,7 @@ license="MIT"
homepage="https://nodejs.org/"
changelog="https://raw.githubusercontent.com/nodejs/node/main/doc/changelogs/CHANGELOG_V${version%%.*}.md"
distfiles="https://nodejs.org/dist/v${version}/node-v${version}.tar.xz"
-checksum=cd6c8fc3ff2606aadbc7155db6f7e77247d2d0065ac18e2f7f049095584b8b46
+checksum=fe1bc4be004dc12721ea2cb671b08a21de01c6976960ef8a1248798589679e16
python_version=3
build_options="ssl libuv icu nghttp2 cares brotli"
reply other threads:[~2025-01-08 0:19 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53887@inbox.vuxu.org \
--to=keepbotting@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).