From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pnpm: update to 8.6.5, fix update-check
Date: Mon, 03 Jul 2023 11:33:36 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44809@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1108 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/44809
pnpm: update to 8.6.5, fix update-check
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### 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, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/44809.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pnpm-44809.patch --]
[-- Type: text/x-diff, Size: 1293 bytes --]
From 3ab381da73828718589305d8d23d49f6108039b4 Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Mon, 3 Jul 2023 11:33:16 +0200
Subject: [PATCH] pnpm: update to 8.6.5, fix update-check
---
srcpkgs/pnpm/template | 4 ++--
srcpkgs/pnpm/update | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
create mode 100644 srcpkgs/pnpm/update
diff --git a/srcpkgs/pnpm/template b/srcpkgs/pnpm/template
index 09d40e5b7124..752950d47f43 100644
--- a/srcpkgs/pnpm/template
+++ b/srcpkgs/pnpm/template
@@ -1,6 +1,6 @@
# Template file for 'pnpm'
pkgname=pnpm
-version=8.6.2
+version=8.6.5
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=c6da9e00697e334b6193c034a5d1508e4c8605b12f249736b13f31139f4f0d73
+checksum=91dd45b4762c73f58f354999867854fcbe7376235474d131080fe391f2eb5227
python_version=3
do_install() {
diff --git a/srcpkgs/pnpm/update b/srcpkgs/pnpm/update
new file mode 100644
index 000000000000..784fc173868c
--- /dev/null
+++ b/srcpkgs/pnpm/update
@@ -0,0 +1,2 @@
+site=https://github.com/pnpm/pnpm/tags
+pattern='/tags/v\K[\d.]+(?=.tar.gz)'
\ No newline at end of file
next reply other threads:[~2023-07-03 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 9:33 Bnyro [this message]
2023-07-03 11:18 ` [PR PATCH] [Closed]: " Duncaen
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-44809@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).