Files

T

Rajiv SahalandGitHub f9ff3248e5 feat: endpoint to update location for existing booking (#25367 )

* feat: init endpoint to update booking location

* chore: update controller

* chore: DTOs for update location endpoint

* chore: add update booking method

* fix: refactor

* feat: service update booking location

* chore: update platform libraries

* chore: update exports

* chore: e2e tests for updating booking location endpoint

* chore: update e2e tests for updating booking location endpoint

* chore: update bookings module

* fixup

* chore: update configs

* fixup: revert changes

* chore: remove unused handlers

* fix: update inputs

* refactor: booking location service

* fixup

* revert: unnecessary changes

* chore: cleanup

* fix: e2e tests

* chore: implement cubic feedback

* chore: implement feedback

* fixup

* chore: more PR feedback

2025-12-22 09:25:00 +00:00

scripts

fix: create event type with output of another create event type (#21273 )

2025-05-16 16:34:44 +03:00

app-store.ts

refactor: Remove circular deps between @calcom/lib and @calcom/features [2] (#24438 )

2025-10-17 06:48:08 -03:00

bookings.ts

chore: Improves the core booking audit architecture by adding new capabilities and simplifying the existing interfaces. (#25872 )

2025-12-18 12:46:24 +00:00

CHANGELOG.md

feat: v2 and atoms attendee defined meeting locations (#17224 )

2024-10-22 13:24:16 +00:00

conferencing.ts

feat: add session endpoint and booking access pbac (#24637 )

2025-12-04 05:45:17 +00:00

emails.ts

feat: Add endpoint to add attendees to existing bookings (#24414 )

2025-10-28 14:16:07 +05:30

event-types.ts

feat: api v2 event type settings - booker bookings limit, emails, round robin reschedule (#24169 )

2025-10-15 17:31:35 +03:00

i18n.ts

fix: Modified teamName to be null when host is not fixed (#24728 )

2025-10-30 14:00:25 +02:00

index.ts

feat: add webhook versioning (#23861 )

2025-12-18 09:36:22 +02:00

organizations.ts

fix: APIV2 team membership - Member not getting added to event-type automatically (#24780 )

2025-11-07 10:50:00 +00:00

package.json

fix: lock package versions and organize devDependencies (#26095 )

2025-12-21 10:18:07 -03:00

pbac.ts

feat: api v2 pbac support (#24402 )

2025-11-06 17:14:55 +00:00

private-links.ts

chore: [Booking Flow Refactor - 5] Move post booking things to separate service BookingEventHandlerService starting with HashedLink usage handling (#24025 )

2025-10-23 15:05:55 +03:00

README.md

fix: create event type with output of another create event type (#21273 )

2025-05-16 16:34:44 +03:00

repositories.ts

refactor: Migrate repositories/services from /lib to /features (#25925 )

2025-12-17 14:14:50 +00:00

schedules.ts

refactor: remove tRPC references from packages/lib (#24553 )

2025-10-27 18:13:25 +00:00

slots.ts

refactor: move handleNotificationWhenNoSlots from trpc to features/slots (#25538 )

2025-12-08 10:54:21 +02:00

tsconfig.json

chore: create standalone i18n utility for platform libraries (#23386 )

2025-08-27 10:55:57 -03:00

vite.config.js

feat: endpoint to update location for existing booking (#25367 )

2025-12-22 09:25:00 +00:00

workflows.ts

chore: Org Team workflows endpoints [v2] (#21329 )

2025-06-13 15:10:44 +02:00

README.md

How to work with platform libraries in Dev

We version this package using NPM: https://www.npmjs.com/package/@calcom/platform-libraries?activeTab=code

Here is the workflow:

If you change platform libraries for the first time, then run yarn local to build them locally for the first time. This will also make v2 api point to the local libraries.
If you change them for the second time, then run yarn build:dev to re-build them.
Once you are happy with platform libraries:

run yarn publish-npm - it will check "@calcom/platform-libraries" version in npm and update it's package.json to the next version and then it will publish the package to npm, update the version of "@calcom/platform-libraries" in the api v2 package.json, reset "@calcom/platform-libraries" to 0.0.0 and run yarn install.

Before Merging to main

Publish Your Version of Libraries on NPM:
- To publish, ensure you are a contributor to the platform libraries' NPM package.
- Authenticate yourself via the CLI using npm auth.
- Increment the version number accordingly.
- Run yarn publish to publish your version.
Once it's published, change back the version in packages/platform/libraries/package.json back to 0.0.0
Run yarn
You should now be using the npm package instead of the locally built version

When to publish new version of platform libraries

New exports in the index.js of platform libraries
Code change in the functions already exported
Prisma schema change breaking implementation of functions in the currently used releases of platform libraries