From: Shan Shaji <s.shaji@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH proxmox_login_manager/pve_flutter_frontend 0/3] chore: add CHANGELOG file and explicit version numbers for path packages
Date: Tue, 23 Sep 2025 14:06:17 +0200 [thread overview]
Message-ID: <20250923120620.279795-1-s.shaji@proxmox.com> (raw)
Since changes are being made to the Flutter app packages, it’s better
to manage path dependencies with proper versioning. To address this,
I added a CHANGELOG file for the proxmox_login_manager package and
specified explicit version numbers wherever the path packages
are referenced.
proxmox_login_manager:
Shan Shaji (2):
chore: bumb version to v1.0.0
chore: add explicit version for dart_client package
CHANGELOG.md | 7 +++
pubspec.lock | 118 +++++++++++++++++++++++++++++++--------------------
pubspec.yaml | 3 +-
3 files changed, 80 insertions(+), 48 deletions(-)
create mode 100644 CHANGELOG.md
pve_flutter_frontend:
Shan Shaji (1):
chore: add explicit version property for path packages
pubspec.lock | 2 +-
pubspec.yaml | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
Summary over all repositories:
5 files changed, 83 insertions(+), 49 deletions(-)
--
Generated by git-murpp 0.8.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-09-23 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 12:06 Shan Shaji [this message]
2025-09-23 12:06 ` [pve-devel] [PATCH proxmox_login_manager 1/2] chore: bumb version to v1.0.0 Shan Shaji
2025-09-23 12:06 ` [pve-devel] [PATCH proxmox_login_manager 2/2] chore: add explicit version for dart_client package Shan Shaji
2025-09-23 12:06 ` [pve-devel] [PATCH pve_flutter_frontend 1/1] chore: add explicit version property for path packages Shan Shaji
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=20250923120620.279795-1-s.shaji@proxmox.com \
--to=s.shaji@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