Release Candidate v12.0

[awana-release-bot]

This PR tracks QA of the release candidate for v12.0.

🍒 All changes to this branch should be cherry-picked from develop.

⚠️ Only add bug fixes, copy edits and translation updates during the QA process.

🌐 Reminder: Please ensure this release branch is synced with Crowdin GitHub Integration before triggering a build.

To sync this branch:

1. Open the Crowdin GitHub Integration settings.
2. Click Edit on the Github integration screen.
3. In the Select Branches for Translation section, make sure this release branch is listed and selected.
4. Click Save to confirm.
5. After saving, click the three dots next to the branch and select Sync branch to immediately create a PR with the translations.

🧪 Create a new Release Candidate build by commenting on this PR with the /build-rc command.

🚧 An initial Release Candidate build will be triggered shortly, and the build URL will be posted here.

🚀 Merging this PR will trigger a release build.

[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/​@​wdio/​browserstack-service@​9.21.0
	npm/​@​osm_borders/​maritime_10000m@​1.1.0
	npm/​@​formatjs/​cli@​6.8.2
	npm/​@​types/​lodash.isequal@​4.5.8
	npm/​@​react-native/​typescript-config@​0.76.9
	npm/​@​react-native/​metro-babel-transformer@​0.76.9
	npm/​@​types/​lint-staged@​13.3.0
	npm/​@​types/​react-native-zeroconf@​0.13.1
	npm/​@​comapeo/​nodejs-mobile-react-native@​18.20.4-2
	npm/​@​types/​react-native-indicators@​0.16.6
	npm/​@​react-native/​metro-config@​0.79.5
	npm/​babel-preset-expo@​54.0.10
	npm/​@​tanstack/​eslint-plugin-query@​5.91.2
	npm/​@​types/​semver@​7.7.1
	npm/​@​react-navigation/​native-stack@​7.3.21
	npm/​@​comapeo/​core-react@​11.0.4
	npm/​@​react-navigation/​native@​7.2.2
	npm/​@​mapeo/​mock-data@​5.0.0
	npm/​@​react-navigation/​bottom-tabs@​7.15.9
	npm/​@​comapeo/​cloud@​0.4.0
	npm/​@​formatjs/​intl-pluralrules@​6.3.1
	npm/​@​types/​jest@​30.0.0
	npm/​@​formatjs/​intl-getcanonicallocales@​3.2.2
	npm/​@​babel/​preset-env@​7.28.5
	npm/​@​types/​mocha@​10.0.10
	npm/​@​formatjs/​intl-locale@​5.3.1
	npm/​@​react-native-documents/​picker@​12.0.1
	npm/​@​types/​react@​19.2.7
	npm/​@​babel/​runtime@​7.27.1 ⏵ 7.28.4
	npm/​@​react-native-vector-icons/​fontisto@​13.0.0
	npm/​@​types/​utm@​1.1.4
	npm/​@​react-native-vector-icons/​octicons@​21.0.0
See 35 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		Critical CVE: WebdriverIO BrowserStack Service has a Command Injection issue in npm @wdio/browserstack-service CVE: GHSA-5c46-x3qw-q7j7 WebdriverIO BrowserStack Service has a Command Injection issue (CRITICAL) Affected versions: < 9.24.0 Patched version: 9.24.0 From: package-lock.json → npm/@wdio/browserstack-service@9.21.0 ℹ Read more on: This package | This alert | What is a critical CVE? 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 support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@wdio/browserstack-service@9.21.0. 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.
Warn		Obfuscated code: npm @browserstack/ai-sdk-node is 100.0% likely obfuscated Confidence: 1.00 Location: Package overview From: package-lock.json → npm/@wdio/browserstack-service@9.21.0 → npm/@browserstack/ai-sdk-node@1.5.17 ℹ 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 support@socket.dev. 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/@browserstack/ai-sdk-node@1.5.17. 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.
Warn		Obfuscated code: npm @react-native/debugger-frontend is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: package-lock.json → npm/@react-native/debugger-frontend@0.81.5 ℹ 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 support@socket.dev. 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/@react-native/debugger-frontend@0.81.5. 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.
Warn		Obfuscated code: npm @react-native/debugger-frontend is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: package-lock.json → npm/@react-native/debugger-frontend@0.81.6 ℹ 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 support@socket.dev. 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/@react-native/debugger-frontend@0.81.6. 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

[awana-release-bot]

🚧 Release candidate build based on 128941e (potential merge of d08c2bd): https://expo.dev/accounts/digidem/projects/comapeo/builds/95732d88-1dad-49ac-aa35-e76df30847c1