From: jlicht@fsfe.org
To: 64611@debbugs.gnu.org
Cc: Jelle Licht <jlicht@fsfe.org>
Subject: [bug#64611] [PATCH v2 2/2] gnu: node-lts: Update to 18.17.0.
Date: Mon, 24 Jul 2023 12:28:01 +0200 [thread overview]
Message-ID: <dbc3d7b427b1f0aed5d922984cb35e9c3f63c40e.1690194338.git.jlicht@fsfe.org> (raw)
In-Reply-To: <4679c971c86cf0ac2ed2f18e9c60f9512e0189c5.1690194338.git.jlicht@fsfe.org>
From: Jelle Licht <jlicht@fsfe.org>
* gnu/packages/node.scm (node-lts): Update to 18.17.0.
---
Changes in v2:
- re-bump node-lts from 18.16.1 to 18.17.0
gnu/packages/node.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/node.scm b/gnu/packages/node.scm
index 91a7d9c700..5f42aabcd3 100644
--- a/gnu/packages/node.scm
+++ b/gnu/packages/node.scm
@@ -738,14 +738,14 @@ (define-public llhttp-bootstrap
(define-public node-lts
(package
(inherit node)
- (version "18.16.0")
+ (version "18.17.0")
(source (origin
(method url-fetch)
(uri (string-append "https://nodejs.org/dist/v" version
"/node-v" version ".tar.gz"))
(sha256
(base32
- "0vcc132z7lkxnw5clmiz6sp6ccmw35pyb69hczphrig5frfmqkva"))
+ "1sblzgjv608dygfdnks2p45fpl7066brw7fm9dd8kd8r09y1baks"))
(modules '((guix build utils)))
(snippet
'(begin
--
2.41.0
next prev parent reply other threads:[~2023-07-24 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 13:58 [bug#64611] [PATCH 0/2] Update node-lts to 18.16.1 [security fixes] jlicht
2023-07-14 14:01 ` [bug#64611] [PATCH 1/2] gnu: llhttp-bootstrap: Update to 6.0.11 jlicht
2023-07-14 14:01 ` [bug#64611] [PATCH 2/2] gnu: node-lts: Update to 18.16.1 jlicht
2023-07-24 10:28 ` [bug#64611] [PATCH v2 1/2] gnu: llhttp-bootstrap: Update to 6.0.11 jlicht
2023-07-24 10:28 ` jlicht [this message]
2023-08-19 20:48 ` [bug#64611] [PATCH v3 " jlicht
2023-08-19 20:48 ` [bug#64611] [PATCH v3 2/2] gnu: node-lts: Update to 18.17.1 jlicht
2023-08-31 18:34 ` bug#64611: " Jelle Licht
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dbc3d7b427b1f0aed5d922984cb35e9c3f63c40e.1690194338.git.jlicht@fsfe.org \
--to=jlicht@fsfe.org \
--cc=64611@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).