fix(deps): update dependency androidx.appcompat:appcompat to v1.7.1

[renovate]

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

---

This PR contains the following updates:

Package	Change	Age	Confidence
androidx.appcompat:appcompat (source)	1.6.1 -> 1.7.1

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Note

Free review on us!

CodeRabbit is offering free reviews until Wed Oct 08 2025 to showcase some of the refinements we've made.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​husky@​9.1.7
	npm/​vue-tsc@​3.1.0
	npm/​unplugin-vue-macros@​2.14.5
	npm/​unplugin-icons@​22.4.2
	npm/​vue-router@​4.5.1
	npm/​base64-arraybuffer@​1.0.2
	npm/​vue-turnstile@​1.0.11
	npm/​unplugin-formkit@​0.3.0
	npm/​tailwind-capacitor@​1.0.9
	npm/​vite-plugin-environment@​1.1.3
	npm/​crypto-random-string@​5.0.0
	npm/​cron-schedule@​5.0.4
	npm/​capacitor-camera-view@​1.2.2
	npm/​vitest@​3.2.4
	npm/​vue-chartjs@​5.3.2
	npm/​country-code-to-flag-emoji@​2.1.0
	npm/​vite-plugin-vue-layouts@​0.11.0
	npm/​vue-demi@​0.14.10
	npm/​postgres@​3.4.7
	npm/​plausible-tracker@​0.3.9
	npm/​pinia@​3.0.3
	npm/​vite@​7.1.9
	npm/​unplugin-vue-router@​0.15.0
	npm/​vite-plugin-vue-devtools@​8.0.2
	npm/​tailwindcss@​4.1.14
	npm/​bun-types@​1.2.23
	npm/​mime@​4.1.0
	npm/​semver@​7.7.2
	npm/​capacitor-secure-storage-plugin@​0.12.0
	npm/​cross-env@​10.1.0
	npm/​dayjs@​1.11.18
	npm/​chart.js@​4.5.0
	npm/​vite-plugin-webfont-dl@​3.11.1
See 24 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		npm/[email protected] has Obfuscated code. Confidence: 0.94 Location: Package overview From: ? → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.