Skip to content

Conversation

@betomoedano
Copy link
Contributor

What does this PR do?

  • Upgrades companion app to Expo SDK 55 and unlocks the latest Liquid Glass features.

Mandatory Tasks (DO NOT REMOVE)

  • I have self-reviewed the code (A decent size PR without self-review might be rejected).
  • I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
  • I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

  • Install dependencies bun I
  • prebuild npx expo prebuild
  • run it npx expo run:ios

@betomoedano betomoedano requested a review from a team as a code owner December 12, 2025 02:42
@CLAassistant
Copy link

CLAassistant commented Dec 12, 2025

CLA assistant check
All committers have signed the CLA.

@graphite-app graphite-app bot added the community Created by Linear-GitHub Sync label Dec 12, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 12, 2025

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Feat/upgrade to sdk 55 canary". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@vercel
Copy link

vercel bot commented Dec 12, 2025

@betomoedano is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 6 files

volnei
volnei previously approved these changes Dec 12, 2025
@volnei
Copy link
Contributor

volnei commented Dec 12, 2025

LGTM! Thank you for your contribution!! ❤️

@volnei volnei enabled auto-merge (squash) December 12, 2025 10:48
@volnei volnei changed the title Feat/upgrade to sdk 55 canary feat: upgrade to sdk 55 canary Dec 12, 2025
@volnei volnei self-requested a review December 12, 2025 18:26
volnei
volnei previously approved these changes Dec 12, 2025
auto-merge was automatically disabled December 14, 2025 18:46

Head branch was pushed to by a user without write access

@betomoedano betomoedano force-pushed the feat/upgrade-to-sdk-55-canary branch from 8f10554 to 67db784 Compare December 14, 2025 18:46
@PeerRich PeerRich enabled auto-merge (squash) December 14, 2025 19:15
@PeerRich PeerRich disabled auto-merge December 14, 2025 19:15
@PeerRich PeerRich merged commit e9c3d7e into calcom:main Dec 14, 2025
28 of 34 checks passed
@PeerRich
Copy link
Member

force merging since this is wrongly tagged for foundation and the /companion folder is a sideproject that is not production relevant

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

Labels

community Created by Linear-GitHub Sync size/XXL

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants