Skip to content

build(expo-example): upgrade Expo example app from SDK 53 to SDK 54#417

Open
imSzukala wants to merge 1 commit intomainfrom
irena/expo-example-upgrade
Open

build(expo-example): upgrade Expo example app from SDK 53 to SDK 54#417
imSzukala wants to merge 1 commit intomainfrom
irena/expo-example-upgrade

Conversation

@imSzukala
Copy link
Copy Markdown
Contributor

Why?

Intercom Android SDK 18.0.0 requires compileSdk 36 and targetSdk 36. The Expo example was on SDK 53 / RN 0.79.6 (compileSdk 35), which cannot build with SDK 18.0.0. This complements #408 which upgraded the bare example app.

How?

Upgrades the Expo example from SDK 53 to SDK 54, which bundles React Native 0.81.5 with compileSdk 36 / targetSdk 36. All Expo-managed dependencies were updated to their SDK 54 compatible versions.

Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@imSzukala imSzukala self-assigned this Apr 10, 2026
@socket-security
Copy link
Copy Markdown

@socket-security
Copy link
Copy Markdown

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 High
License policy violation: npm typescript under CC-BY-4.0

License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt)

From: examples/expo-example/package.jsonnpm/typescript@5.9.3

ℹ 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/typescript@5.9.3. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants