From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pnpm: update to 8.6.0
Date: Tue, 30 May 2023 11:38:52 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44165@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
There is a new pull request by Bnyro against master on the void-packages repository
https://github.com/Bnyro/void-packages pnpm
https://github.com/void-linux/void-packages/pull/44165
pnpm: update to 8.6.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
cc @fnogcps
The 7.x branch of pnpm is no longer maintained (according to https://pnpm.io/versions), and I couldn't find any reasons to not switch to the 8.x branch.
pnpm 8 dropped support for nodejs 14, but since we're already using nodejs 16 that shouldn't be an issue.
A patch file from https://github.com/void-linux/void-packages/pull/44165.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pnpm-44165.patch --]
[-- Type: text/x-diff, Size: 935 bytes --]
From 37c6aed1cf8f304988c729d76a6bcf270a50d75f Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Tue, 30 May 2023 11:34:12 +0200
Subject: [PATCH] pnpm: update to 8.6.0
---
srcpkgs/pnpm/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/pnpm/template b/srcpkgs/pnpm/template
index a6551bc553a0..5e3f10c0aa8b 100644
--- a/srcpkgs/pnpm/template
+++ b/srcpkgs/pnpm/template
@@ -1,6 +1,6 @@
# Template file for 'pnpm'
pkgname=pnpm
-version=7.30.5
+version=8.6.0
revision=1
build_style=fetch
hostmakedepends="nodejs jq"
@@ -10,7 +10,7 @@ maintainer="reback00 <reback00@protonmail.com>"
license="MIT"
homepage="https://pnpm.io/"
distfiles="https://registry.npmjs.org/pnpm/-/pnpm-${version}.tgz"
-checksum=c8d730294f671574458704cd56e81dc0eb8d345a444e4c7a728d8d2cdc4f5045
+checksum=1e9c17c34c2eebaba02e78b619e296db08d302c296e58c2f51b0cd4e3e5bcda2
python_version=3
do_install() {
next reply other threads:[~2023-05-30 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 9:38 Bnyro [this message]
2023-06-09 1:42 ` [PR PATCH] [Merged]: " classabbyamp
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-44165@inbox.vuxu.org \
--to=bnyro@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).