Files

T

b1eb5a2809 feat: api v2 POST booking attendees endpoint (#27759 )

* feat: add booking attendee endpoint

* chore: add attendee added email for add guests handler

* cleanup

* fix: restore BookingPbacGuard to prevent IDOR vulnerability in booking attendees endpoint

Co-Authored-By: unknown <>

* chore: implement review feedback, add a core service for booking attendees endpoint

* chore: implement PR feedback

* fix: dont reuse add guests handler instead add logic to add attendee function

* fix: revert previous changes

* chore: implement cubic feedback

* fix: e2e tests

* fix: e2e tests

* fix: remove convertTRPCErrorToErrorWithCode not needed

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

2026-02-17 20:46:18 +00:00

scripts

Prefix node protocol (#26391 )

2026-01-02 12:47:00 +00:00

app-store.ts

perf: convert services to factory functions and add TypeScript project references (#26117 )

2026-01-15 11:28:05 -03:00

bookings.ts

feat: api v2 POST booking attendees endpoint (#27759 )

2026-02-17 20:46:18 +00:00

calendars.ts

feat: add CalendarsTasker with sync and trigger.dev versions (#26854 )

2026-01-19 16:20:05 +02: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

fix: Add email verification requirement for API v1 and v2 email updates (#24988 )

2026-01-08 15:51:11 +00:00

errors.ts

feat: OAuth2 controller api v2 + refactor oAuth Trpc handlers (#25989 )

2026-01-07 08:05:21 -03:00

event-types.ts

feat: Troubleshooter atom (#27497 )

2026-02-06 17:34:58 +02:00

i18n.ts

Prefix node protocol (#26391 )

2026-01-02 12:47:00 +00:00

index.ts

refactor: decouple @calcom/features from @calcom/trpc/server (#27751 )

2026-02-10 09:28:37 -03:00

organizations.ts

feat: move platform active billing logic to services (#27704 )

2026-02-06 12:45:40 +00:00

package.json

refactor: platform billing jobs tasks constants (#27190 )

2026-01-23 12:54:05 +00: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: Move repositories from @calcom/lib to @calcom/features domain folders (#27570 )

2026-02-09 08:41:04 -03:00

schedules.ts

feat: Troubleshooter atom (#27497 )

2026-02-06 17:34:58 +02:00

slots.ts

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

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

tasker.ts

refactor: platform billing jobs tasks constants (#27190 )

2026-01-23 12:54:05 +00:00

tsconfig.json

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

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

vite.config.js

refactor: platform billing jobs tasks constants (#27190 )

2026-01-23 12:54:05 +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