Bump expo-status-bar from 1.12.1 to 55.0.4

[dependabot]

Bumps expo-status-bar from 1.12.1 to 55.0.4.

Changelog

Sourced from expo-status-bar's changelog.

55.0.4 — 2026-02-25

💡 Others

• Deprecated and turned into no-ops the backgroundColor, networkActivityIndicatorVisible and translucent StatusBar props, as well as the setStatusBarBackgroundColor, setStatusBarNetworkActivityIndicatorVisible and setStatusBarTranslucent functions. (#43276 by @​zoontek)

55.0.3 — 2026-02-16

This version does not introduce any user-facing changes.

55.0.2 — 2026-01-26

This version does not introduce any user-facing changes.

55.0.1 — 2026-01-22

This version does not introduce any user-facing changes.

55.0.0 — 2026-01-21

This version does not introduce any user-facing changes.

3.0.9 - 2025-12-05

This version does not introduce any user-facing changes.

3.0.8 — 2025-09-11

This version does not introduce any user-facing changes.

3.0.7 — 2025-09-02

This version does not introduce any user-facing changes.

3.0.6 — 2025-08-31

This version does not introduce any user-facing changes.

3.0.5 — 2025-08-27

This version does not introduce any user-facing changes.

3.0.4 — 2025-08-25

This version does not introduce any user-facing changes.

3.0.3 — 2025-08-18

This version does not introduce any user-facing changes.

... (truncated)

Commits

• See full diff in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 778350a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	del-cli@​5.1.0
	deepmerge@​4.3.1
	crc-32@​1.2.2
	credit-card-type@​9.1.0
	card-validator@​8.1.1
	concurrently@​8.2.2
	asn1js@​3.0.6
	asn1js@​3.0.7

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		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (npm metadata) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/package.json) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: pnpm-lock.yaml → npm/@babel/core@7.29.0 → npm/caniuse-lite@1.0.30001695 ℹ Read more on: This package | This alert | What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001695. 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		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (npm metadata) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/package.json) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: pnpm-lock.yaml → npm/caniuse-lite@1.0.30001777 ℹ Read more on: This package | This alert | What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001777. 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

[matt-evervault]

Dependabot review: expo-status-bar 1.12.1 → 55.0.4

Verdict: safe to merge. No code changes were required.

Usage audit

The package is only consumed in one place in the entire repo:

• examples/react-native-example/App.tsx
  • import { StatusBar } from "expo-status-bar";
  • <StatusBar style="auto" />

It is not used by any of the shipped @evervault/* SDKs — only by the React Native example app for local development.

Changelog review (1.12.1 → 55.0.4)

The major-version jump (1.x → 55.x) is not driven by API breakage; it's Expo's package-version unification to align with the Expo SDK release line (SDK 55).

Notable items between these versions:

• 55.0.4 — deprecated and turned into no-ops the backgroundColor, networkActivityIndicatorVisible, and translucent props on StatusBar, plus the equivalent setStatusBar* setter functions. We do not use any of these.
• 55.0.3 / 55.0.2 / 55.0.1 / 55.0.0 / 3.x point releases — "no user-facing changes" per the changelog.
• The style prop API is unchanged across this range, so <StatusBar style="auto" /> continues to behave identically.
• Future v56 will fully remove the props deprecated in 55.0.4 and migrate setStatusBarStyle/setStatusBarHidden to static methods — none of which we use today.

Security / supply chain

• Resolution + integrity hash present in pnpm-lock.yaml.
• New transitive dep introduced: react-native-is-edge-to-edge@1.3.1 (a small helper that detects edge-to-edge mode on Android). No security advisories for it; peer-deps only on react/react-native.
• No suspicious or unexpected new dependencies otherwise.

Compatibility note (non-blocking)

The catalog still pins expo: ~52.0.47. Expo SDK 52 normally bundles expo-status-bar 2.x, while 55.0.4 is the SDK 55 release. The package is a thin wrapper with no expo-modules-core peer constraint, and our only usage (style="auto") is unaffected, so this version skew is fine for the example app — but worth mentioning in case the example is later upgraded to SDK 55 wholesale.

Build / typecheck

• pnpm install --frozen-lockfile ✅
• pnpm run build (recursive across @evervault/* packages) ✅
• pnpm run typecheck (recursive across @evervault/* packages) ✅
• Pre-existing typecheck errors in examples/react-native-example (ThreeDSecureModal, CardDebug.tsx) are present on master as well and are unrelated to this bump.

No code changes were necessary.

---

Generated by Claude Code