fix: Update libphonenumber-js to fix Australian numbers validation error

[retrogtx]

What does this PR do?

Updates the libphonenumber-js to 1.11.18

• Fixes libphonenumber-js version out of date. Australian numbers starting with +614943 are not validating in Calcom #18703 (GitHub issue number)

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?

• Are there environment variables that should be set?
• What are the minimal test data to have?
• What is expected (happy path) to have (input and output)?
• Any other important info that could help to test that PR

[vercel]

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

A member of the Team first needs to authorize it.

[github-actions]

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:

Unknown release type "Fix" found in pull request title "Fix: Update libphonenumber-js to fix Australian numbers validation error". 

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

[graphite-app]

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (01/17/25)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add community label" took an action on this PR • (01/17/25)

1 label was added to this PR based on Keith Williams's automation.

[Ryukemeister]

@retrogtx had some questions here. Since we're going from version 1.10 to 1.11 can you make sure there are no breaking changes? Additionally can you make sure if something that we already use from the current version has not been deprecated in the next version and that there is backwards compatibility? Reason being if there's any such kind of change it would affect phone input for the whole app in the next release.

[retrogtx]

On it

[Ryukemeister]

It seems like #18724 fixes the same issue

[retrogtx]

It seems like #18724 fixes the same issue

yep, that looks fine to me as well

we do need to add it in package.json too
along with a change in the schema

the person who raised the issue has given the solution as well actually

[retrogtx]

@retrogtx had some questions here. Since we're going from version 1.10 to 1.11 can you make sure there are no breaking changes? Additionally can you make sure if something that we already use from the current version has not been deprecated in the next version and that there is backwards compatibility? Reason being if there's any such kind of change it would affect phone input for the whole app in the next release.

there is a patch in package.json

"libphonenumber-js@^1.10.51": "patch:libphonenumber-js@npm%3A1.10.51#./.yarn/patches/libphonenumber-js-npm-1.10.51-4ff79b15f8.patch",

"libphonenumber-js@^1.10.12": "patch:libphonenumber-js@npm%3A1.10.51#./.yarn/patches/libphonenumber-js-npm-1.10.51-4ff79b15f8.patch",

I suppose we can get rid of this too, but need to get rid of the actual patch also
Other than the two places, I do not think we use the libphonenumber-js package anywhere

Lmk if you see the latest code works fine as well

[anikdhabal]

Fixed by this:- #18757