From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Francois Perrad <francois.perrad@gadz.org>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/quickjs: bump to version 2025-09-13
Date: Mon, 06 Apr 2026 19:26:30 +0200 [thread overview]
Message-ID: <90f9582eb5fef06765158333df520c91@free.fr> (raw)
In-Reply-To: <20260406100822.7845-1-francois.perrad@gadz.org>
Hi Francois,
Thanks for the patch.
On 06/04/2026 12:08, Francois Perrad via buildroot wrote:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
[...]
> diff --git a/package/quickjs/quickjs.mk b/package/quickjs/quickjs.mk
> index e2170b297..511f14245 100644
> --- a/package/quickjs/quickjs.mk
> +++ b/package/quickjs/quickjs.mk
> @@ -4,7 +4,7 @@
> #
>
> ################################################################################
>
> -QUICKJS_VERSION = 2025-04-26
> +QUICKJS_VERSION = 2025-09-13
Looking at:
https://autobuild.buildroot.org/stats/master.html
It seems there is 7 CVEs assigned to the old version,
fixed by this new version. CVE-2025-62490 to CVE-2025-62496
inclusive.
Could you mark this commit as a "security bump", and
add in the commit log a link to the change log
https://bellard.org/quickjs/Changelog
and references to fixed CVEs, please?
> QUICKJS_SOURCE = quickjs-$(QUICKJS_VERSION).tar.xz
> QUICKJS_SITE = https://bellard.org/quickjs
> QUICKJS_LICENSE = MIT
> --
> 2.43.0
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-04-06 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 10:08 [Buildroot] [PATCH] package/quickjs: bump to version 2025-09-13 Francois Perrad via buildroot
2026-04-06 17:26 ` Julien Olivain via buildroot [this message]
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=90f9582eb5fef06765158333df520c91@free.fr \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=francois.perrad@gadz.org \
--cc=ju.o@free.fr \
/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