From: "Shan Shaji" <s.shaji@proxmox.com>
To: "Dominik Csapak" <d.csapak@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH proxmox_dart_api_client 1/2] chore: upgrade dependencies
Date: Tue, 02 Jun 2026 11:15:14 +0200 [thread overview]
Message-ID: <DIYG6UCF9BFI.33A4GZDQR7RQL@proxmox.com> (raw)
In-Reply-To: <2c138f6f-4926-4e7e-a7a4-9283c6eca944@proxmox.com>
On Tue Jun 2, 2026 at 10:49 AM CEST, Dominik Csapak wrote:
> IMO ok, but can you include a single sentence how you updated the
> dependencies (just for reference)
>
Ahh, sorry! I will send a v2 with an updated commit message. Since I have
changed the SDK, `flutter pub get` updated it as some packages may no longer
be compatible with the new version.
Thank you so much for the reviews. I will send a v2
next prev parent reply other threads:[~2026-06-02 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 15:09 [PATCH proxmox{_login_manager,_dart_api_client}/pve_flutter_frontend 0/7] upgrade dependencies based on flutter v3.41 and migrate deprecated members Shan Shaji
2026-04-10 15:09 ` [PATCH pve_flutter_frontend 1/4] chore: upgrade dependencies based on flutter v3.41 Shan Shaji
2026-06-02 8:50 ` Dominik Csapak
2026-04-10 15:09 ` [PATCH pve_flutter_frontend 2/4] fix: breaking changes due to the upgrade of font_awesome_flutter to v11 Shan Shaji
2026-06-02 8:54 ` Dominik Csapak
2026-04-10 15:09 ` [PATCH pve_flutter_frontend 3/4] fix: migrate to UIScene lifecycle for iOS 26+ compatibility Shan Shaji
2026-04-10 15:09 ` [PATCH pve_flutter_frontend 4/4] chore: use latest ndkVersion from flutter Shan Shaji
2026-04-10 15:09 ` [PATCH proxmox_login_manager 1/1] chore: upgrade dependencies Shan Shaji
2026-04-10 15:09 ` [PATCH proxmox_dart_api_client 1/2] " Shan Shaji
2026-06-02 8:49 ` Dominik Csapak
2026-06-02 9:15 ` Shan Shaji [this message]
2026-04-10 15:09 ` [PATCH proxmox_dart_api_client 2/2] deps: add objective_c dependency to access NSError's code property Shan Shaji
2026-06-02 8:48 ` Dominik Csapak
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=DIYG6UCF9BFI.33A4GZDQR7RQL@proxmox.com \
--to=s.shaji@proxmox.com \
--cc=d.csapak@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