chore(deps): update dependency react-native-dotenv to v3.4.12

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-native-dotenv	3.4.11 → 3.4.12

---

Release Notes

dotenvx/react-native-dotenv (react-native-dotenv)

v3.4.12

Compare Source

• updated readme (#​584)
• Update package.json

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• Branch creation
  • Between 08:00 AM and 11:59 AM, only on Tuesday (* 8-11 * * 2)
• 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: implementations/react-native-sdk/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @implementation/react-native-sdk@0.0.0
npm error Found: react@18.3.1
npm error node_modules/react
npm error   react@"19.2.3" from the root project
npm error   peer react@"*" from @react-native/virtualized-lists@0.76.9
npm error   node_modules/@react-native/virtualized-lists
npm error     @react-native/virtualized-lists@"0.76.9" from react-native@0.76.9
npm error     node_modules/react-native
npm error       react-native@"0.84.0" from the root project
npm error       2 more (@react-native/virtualized-lists, @react-native-async-storage/async-storage)
npm error   3 more (react-native, react-shallow-renderer, react-test-renderer)
npm error
npm error Could not resolve dependency:
npm error @react-native-clipboard/clipboard@"1.16.3" from the root project
npm error
npm error Conflicting peer dependency: react@19.2.3
npm error node_modules/react
npm error   peer react@"^19.2.3" from react-native@0.84.0
npm error   node_modules/react-native
npm error     react-native@"0.84.0" from the root project
npm error     peer react-native@">= 0.61.5" from @react-native-clipboard/clipboard@1.16.3
npm error     node_modules/@react-native-clipboard/clipboard
npm error       @react-native-clipboard/clipboard@"1.16.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-11T16_45_03_772Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-11T16_45_03_772Z-debug-0.log

[bito-code-review]

Code Review Agent Run #513030

Actionable Suggestions - 0

Review Details

• Files reviewed - 1 · Commit Range: f3ca621..f3ca621

  • implementations/react-native-sdk/package.json
• Files skipped - 0
• Tools

  • Whispers (Secret Scanner) - ✔︎ Successful
  • Detect-secrets (Secret Scanner) - ✔︎ Successful

---

Bito Usage Guide

Commands

Type the following command in the pull request comment and save the comment.

• /review - Manually triggers a full AI review.

• /pause - Pauses automatic reviews on this pull request.

• /resume - Resumes automatic reviews.

• /resolve - Marks all Bito-posted review comments as resolved.

• /abort - Cancels all in-progress reviews.

Refer to the documentation for additional commands.

Configuration

This repository uses Default Agent You can customize the agent settings here or contact your Bito workspace admin at jared.jolton@contentful.com.

Documentation & Help

• Customize agent settings
• Review rules
• General documentation
• FAQ

AI Code Review powered by

[bito-code-review]

Impact Analysis by Bito

Cross-Repository Impact Analysis

What Changed	Impact of Change	Suggested Review Actions
Minor patch version bump of react-native-dotenv from 3.4.11 to 3.4.12	- No cross-repo consumers found for react-native-sdk: searchCode for 'react-native-sdk' returned zero hits across organization; react-native-sdk appears to be an internal monorepo package with no external consumers	- Verify react-native-sdk is not published as a public/consumed npm package - Check if any internal services reference react-native-sdk via package.json dependencies - Confirm .env loading behavior remains consistent after the patch upgrade

Code Paths Analyzed

Impact:
Low impact. A patch version bump of react-native-dotenv with no breaking changes (changelog shows only 'updated readme' and 'Update package.json'). The library is used by react-native-sdk for loading environment variables from .env files into React Native builds via Babel transformation.

Flow:
react-native-dotenv (Babel plugin) → babel.config.js configures it → used at build time to inline .env variables into React Native bundle

Direct Changes (Diff Files):
• implementations/react-native-sdk/package.json [9-10] — Updated react-native-dotenv dependency from 3.4.11 to 3.4.12 (patch version bump with only documentation/package updates, no functional changes)

Repository Impact:
• implementations/react-native-sdk: Single package within this monorepo affected by the dependency bump. No other packages depend on react-native-sdk externally.

Cross-Repository Dependencies:
• None.

Database/Caching Impact:
• None

API Contract Violations:
• None.

Infrastructure Dependencies:
• Babel build pipeline - react-native-dotenv is a Babel plugin that transforms import statements for .env files at build time
• React Native Metro bundler configuration (metro.config.js references babel)

Additional Insights:
• Security / dependency hygiene: Running 'pnpm update react-native-dotenv' or similar to upgrade to latest patch is a standard maintenance practice. Version 3.4.12 appears safe and non-breaking.
• Breaking changes in v4.0.0 (not in use): The library's changelog shows major v4.0.0 had breaking changes (process.env.X inlining behavior, removed whitelist/blacklist options). This PR stays on v3.x so those changes don't apply. Monitor for future v4 upgrades.

Testing Recommendations

Frontend Impact:
• Verify .env files load correctly in React Native development and production builds after the patch upgrade
• Confirm Metro bundler processes environment variables consistently (no inlining errors or missing vars)

Service Integration:
• None.

Data Serialization:
• None.

Privacy Compliance:
• Ensure sensitive values in .env files remain properly loaded and not exposed in bundle output

Backward Compatibility:
• No breaking changes expected - this is a patch version with only readme/package updates per changelog
• Existing .env configurations and babel.config.js setup should continue working without modification

OAuth Functionality:
• None

Reliability Testing:
• None

Additional Insights:
• No specific test changes required for this patch bump - standard React Native E2E tests covering environment variable loading are sufficient
• Consider running 'pnpm dedupe' after the upgrade to ensure optimal dependency resolution

_{Analysis based on known dependency patterns and edges. Actual impact may vary.}

[bito-code-review]

✅ Review Settings Overridden

Status: Overridden Successfully

Guidelines:

• Accepted:

  • General : Review Posture, Repo Truth And Boundaries, Domain Invariants

  • Language : typescript= TypeScript Review Evidence

Note: Extra guidelines beyond 3 general purpose guidelines and 1 language specific guideline per language are not processed. Guidelines are fetched from the source branch.