all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Shan Shaji <s.shaji@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve_flutter_frontend v1] chore: update `compileSdkVersion` to 35 and `targetSdkVersion` to 36
Date: Thu,  3 Jul 2025 16:36:28 +0200	[thread overview]
Message-ID: <175155337073.1388227.5992797591682509235.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250702091056.60732-1-s.shaji@proxmox.com>

On Wed, 02 Jul 2025 11:10:56 +0200, Shan Shaji wrote:
> The current target API level is 34(Android 14). According to
> google play requirements the target API level should be
> within one year of latest Android release.
> 
> To fix the issue update `compileSdkVersion` to 35 (Android 15)
> and `targetSdkVersion` to API level 36 (Android 16). The
> `compileSdkVersion` was not updated to API level 36 as
> `biometric_storage` [5]  plugin's  compileSdk is 35.
> 
> [...]

Applied, thanks!

[1/1] chore: update `compileSdkVersion` to 35 and `targetSdkVersion` to 36
      commit: a2bcbdfb809e4ab9a39224296eb6af88eee45a51


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2025-07-03 14:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02  9:10 [pve-devel] " Shan Shaji
2025-07-03 14:03 ` Dominik Csapak
2025-07-03 14:20   ` Tim Marx
2025-07-03 14:28     ` Thomas Lamprecht
2025-07-03 14:25   ` Thomas Lamprecht
2025-07-03 14:45     ` Dominik Csapak
2025-07-03 14:56       ` Thomas Lamprecht
2025-07-03 15:18         ` Tim Marx
2025-07-04  6:52           ` Shan Shaji
2025-07-04  8:53           ` Thomas Lamprecht
2025-07-04 11:15             ` Shan Shaji
2025-07-07  9:51               ` Shan Shaji
2025-07-03 14:36 ` Thomas Lamprecht [this message]

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=175155337073.1388227.5992797591682509235.b4-ty@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.shaji@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal