Github messages for voidlinux
 help / color / mirror / Atom feed
From: 0cool-f <0cool-f@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pnpm update
Date: Tue, 13 Jun 2023 15:33:48 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44407@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

There is a new pull request by 0cool-f against master on the void-packages repository

https://github.com/0cool-f/void-packages patch-1
https://github.com/void-linux/void-packages/pull/44407

pnpm update
pnpm reverted pnpm-lock v6.1 to v6.0 https://github.com/pnpm/pnpm/issues/6648 it's suggested to upgrade to v8.6.2

#### Testing the changes
- I tested the changes in this PR: **YES**

A patch file from https://github.com/void-linux/void-packages/pull/44407.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-44407.patch --]
[-- Type: text/x-diff, Size: 1072 bytes --]

From b05696814e61f6acd2246ceb7e5382244ee1e6b0 Mon Sep 17 00:00:00 2001
From: Fabio Di Giorgio <20709003+0cool-f@users.noreply.github.com>
Date: Tue, 13 Jun 2023 15:31:06 +0200
Subject: [PATCH] pnpm update

pnpm reverted pnpm-lock v6.1 to v6.0 https://github.com/pnpm/pnpm/issues/6648 it's suggested to upgrade to v8.6.2
---
 srcpkgs/pnpm/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/pnpm/template b/srcpkgs/pnpm/template
index f3e52bc62974..09d40e5b7124 100644
--- a/srcpkgs/pnpm/template
+++ b/srcpkgs/pnpm/template
@@ -1,6 +1,6 @@
 # Template file for 'pnpm'
 pkgname=pnpm
-version=8.6.1
+version=8.6.2
 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=5380612e01e0a3029991d3f329f07429313f4825de47b885b4bb3d1aec9e44e1
+checksum=c6da9e00697e334b6193c034a5d1508e4c8605b12f249736b13f31139f4f0d73
 python_version=3
 
 do_install() {

             reply	other threads:[~2023-06-13 13:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 13:33 0cool-f [this message]
2023-06-13 15:29 ` Bnyro
2023-06-13 23:02 ` [PR PATCH] [Updated] pnpm: update to 8.6.2 0cool-f
2023-06-13 23:04 ` 0cool-f
2023-06-13 23:07 ` 0cool-f
2023-06-15 12:28 ` Bnyro
2023-06-15 12:29 ` Bnyro
2023-06-15 12:30 ` Bnyro
2023-06-15 12:30 ` Bnyro
2023-06-15 16:24 ` [PR PATCH] [Updated] " 0cool-f
2023-06-15 16:33 ` 0cool-f
2023-06-15 20:06 ` paper42
2023-06-16 11:25 ` [PR PATCH] [Updated] " 0cool-f
2023-06-22 10:56 ` [PR PATCH] [Merged]: " 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-44407@inbox.vuxu.org \
    --to=0cool-f@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).