From: Markus Frank <m.frank@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH novnc 3/3] bump version to 1.4.0-1
Date: Thu, 2 Feb 2023 10:57:07 +0100 [thread overview]
Message-ID: <20230202095707.18718-4-m.frank@proxmox.com> (raw)
In-Reply-To: <20230202095707.18718-1-m.frank@proxmox.com>
Signed-off-by: Markus Frank <m.frank@proxmox.com>
---
debian/changelog | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 04939cd..e8cb27c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+novnc-pve (1.4.0-1) bullseye; urgency=medium
+
+ * upgrade noVNC and patches to new 1.4.0 upstream release
+
+ * check for package.json instead of VERSION in Makefile
+
+ -- Proxmox Support Team <support@proxmox.com> Thu, 02 Feb 2023 10:06:55 +0200
+
novnc-pve (1.3.0-3) bullseye; urgency=medium
* skip confirmation in start button
--
2.30.2
next prev parent reply other threads:[~2023-02-02 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 9:57 [pve-devel] [PATCH novnc 0/3] upgrade to v1.4.0 Markus Frank
2023-02-02 9:57 ` [pve-devel] [PATCH novnc 1/3] replaced check for VERSION file with check for package.json Markus Frank
2023-02-02 9:57 ` [pve-devel] [PATCH novnc 2/3] upgrade novnc and patches to 1.4.0 Markus Frank
2023-02-02 9:57 ` Markus Frank [this message]
2023-02-08 16:02 ` [pve-devel] applied-series: [PATCH novnc 0/3] upgrade to v1.4.0 Thomas Lamprecht
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=20230202095707.18718-4-m.frank@proxmox.com \
--to=m.frank@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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