calcom/cal.diy
30.0
Weak · 14 November 2026
334.1k
lines of production code
TypeScript
primary language
5
measurements over time
What this system is
Features
API v2 Webhooks Controller and E2E Tests
This change introduces the API v2 Webhooks controller, exposing endpoints to create, read, update, and delete webhooks for the authenticated user. The implementation includes the controller logic, input/output DTOs, and guards to ensure users can only access their own webhooks. Additionally, comprehensive end-to-end tests are added to verify the correct behavior of these endpoints, including error handling for unauthorized access and non-existent resources.
apps/api/v2/src/modules/webhooks/controllers · high confidence
API v2 introduces Out-of-Office entry management
The API v2 now supports creating, updating, retrieving, and deleting Out-of-Office (OOO) entries. Users can define OOO periods with start and end times, optional notes, and specific reasons (such as vacation, sick leave, or travel). The system enforces business rules including ensuring the start date is before the end date, preventing duplicate entries for the same time slot, and blocking redirects to oneself. Additionally, pagination and sorting by start or end time are supported for listing entries.
apps/api/v2/src/modules/ooo · high confidence
API v2 slots controller introduces worker-based availability and dual slot formats
The API v2 slots controller now supports retrieving available slots in two formats: a simple time-point list or a start/end time range, selectable via the \slotFormat\ query parameter. To improve performance, the availability lookup can be offloaded to background worker threads (controlled by the \enableSlotsWorkers\ environment variable), falling back to the synchronous service in E2E tests or when workers are disabled. The controller also handles slot reservation by setting a \uid\ cookie and allows deletion of selected slots.
apps/api/v2/src/modules/slots/slots-2024-04-15/controllers · high confidence
Add 'Wipe Today' button to cancel today's bookings
The WipeMyCalOther app now includes a 'Wipe Today' button that appears on the bookings page when there are upcoming meetings. Clicking this button opens a confirmation dialog that allows users to cancel all scheduled meetings for the current day. The action is performed via a direct API call to the integration's wipe endpoint, providing immediate feedback through toast notifications and invalidating the local bookings cache upon completion.
apps/web/components/apps/wipemycalother · high confidence
Add API v2 endpoint to update destination calendars
The API v2 now exposes a PUT /v2/destination-calendars endpoint that allows users to update their destination calendar by specifying the integration type, external ID, and an optional delegation credential ID. This change introduces the controller and corresponding end-to-end tests for this specific update operation, enabling programmatic management of the calendar used for booking destinations.
apps/api/v2/src/modules/destination-calendars/controllers · high confidence
Add delegation credential support to destination calendar inputs
The API now accepts an optional \delegationCredentialId\ field when creating or updating destination calendars. This allows users to associate a specific delegation credential with Apple, Google, or Office 365 calendar integrations, enabling domain-wide delegation scenarios for Google services.
apps/api/v2/src/modules/destination-calendars/inputs · high confidence
Add internal v2 timezones endpoint with Redis caching
The API v2 now includes a new internal endpoint at /v2/timezones that retrieves a list of city timezones. This feature is implemented via a new TimezonesController and TimezonesService, which leverage Redis to cache the timezone data for 24 hours to improve performance. The endpoint is marked as excluded from public API documentation, indicating it is intended for internal use by atoms.
apps/api/v2/src/modules/timezones · high confidence
Add loading skeleton for the Apps homepage
The Apps homepage now displays a structured loading skeleton while content is being fetched. This improves the perceived performance by showing placeholders for the featured categories, most popular apps, and all apps sections before the actual data renders.
apps/web/app/(use-page-wrapper)/apps/(homepage) · high confidence
Add push notifications settings page
A new page has been added at /settings/my-account/push-notifications to manage push notification preferences. This page renders the PushNotificationsView component and includes metadata generation for the route.
apps/web/app/(use-page-wrapper)/settings/(settings-layout)/my-account/push-notifications · high confidence
Add server-side rendered booking page for link/slug routes
A new server-side rendered page component has been added for the \/d/\[link\]/\[slug\]\ route. This page fetches booking and event data using the existing server-side logic and renders the booking type view, while also generating dynamic metadata for SEO and browser tabs based on the event title and profile name.
apps/web/app/(booking-page-wrapper)/d · high confidence
Add static Icons Showcase page
A new static /icons page has been added to the application, displaying a grid of available Lucide icons (both regular and filled variants) using the @calcom/ui Icon component. The page is configured as a force-static route to improve performance and caching, and includes metadata generation for SEO.
apps/web/app/icons · high confidence
Add team and user filtering capabilities for event types
This change introduces new logic to parse and validate query parameters for filtering event types by teams, users, and unique provider IDs. It adds a new \getTeamsFiltersFromQuery\ utility that normalizes string and array inputs into sorted lists, ensuring consistent caching behavior for React Query. Additionally, it includes a helper function \hasFilter\ to check for the presence of any active filters and defines TypeScript types for event type filters including team associations.
packages/features/filters · high confidence
Add webhook output DTOs for API v2
This change introduces the output Data Transfer Objects (DTOs) for the API v2 webhook module, defining the structure of webhook responses for users, event types, teams, and OAuth clients. It establishes a base \WebhookOutputDto\ that includes fields such as \id\, \payloadTemplate\, \triggers\ (as an array of \WebhookTriggerEvents\), \subscriberUrl\, \active\ status, and an optional \secret\. Specific response DTOs are added for each entity type (e.g., \EventTypeWebhookOutputResponseDto\, \UserWebhookOutputResponseDto\) to standardize the API response format with status indicators and nested data structures.
apps/api/v2/src/modules/webhooks/outputs · high confidence
Added /more page with server-side rendering
A new /more page has been introduced, implemented as a server component that renders the existing MorePageView. The page includes metadata generation for SEO and accessibility, ensuring it is properly indexed and described within the application.
apps/web/app/(use-page-wrapper)/more · high confidence
Added DateRangeFilter playground for testing date restrictions
A new playground page has been added to the admin settings to demonstrate and test the DateRangeFilter component's behavior. This page allows users to interact with four specific scenarios—'past', 'future', 'any', and 'customOnly'—to verify how date selection restrictions and preset visibility change based on the configured range option.
apps/web/app/(use-page-wrapper)/settings/(admin-layout)/admin/playground/date-range-filter · high confidence
Added E2E session warmup page
A new page at /e2e/session-warmup has been added to the web application to facilitate end-to-end testing. This page triggers NextAuth session callbacks (jwt and session) to populate session data with profile and organization details, ensuring the session is ready for tests. It is gated to only function when the NEXT\_PUBLIC\_IS\_E2E environment variable is set to 1 or when running in development mode; otherwise, it returns a 404.
apps/web/app/e2e · high confidence
Added EventReservationSchema component for structured data
A new React component, EventReservationSchema, has been added to the web application's schema components. This component generates JSON-LD structured data for event reservations, mapping booking details such as reservation ID, event name, time, organizer, attendees, and status into the Schema.org EventReservation type. This enables search engines to better understand and display reservation information.
apps/web/components/schemas · high confidence
Added Google Calendar integration service
A new GCalService has been introduced to handle Google Calendar OAuth flows. This service retrieves the necessary client credentials from the application repository and constructs an OAuth2 client, enabling the platform to interact with Google Calendar for users who have signed up with Google.
apps/api/v2/src/modules/apps/services · high confidence
Added Google login configuration constants
The server-side application now exposes configuration constants for Google authentication, including client ID, client secret, and an enabled flag, which are derived from environment variables to control whether Google login is active.
apps/web/server/lib · high confidence
Added RenderCounter debugging component
A new RenderCounter component has been added to the debugging package to help developers monitor component render frequency. This utility displays a count of how many times a component has rendered, allowing developers to identify unnecessary re-renders or unexpected state resets without triggering additional renders itself.
packages/debugging · high confidence
Added Snaplet configuration and data transformation scripts
Introduced a new \.snaplet\ directory containing configuration files (\config.json\, \manifest.json\) and a \transform.ts\ script to facilitate safe database cloning. The configuration specifies the project ID and target local PostgreSQL database, while the transformation script uses the Snaplet Copycat library to anonymize sensitive data (such as tokens, secrets, and emails) and generate realistic synthetic values for fields like names, slugs, and dates across various database tables including Accounts, Bookings, and Credentials.
.snaplet · high confidence
Added Teams Repository for v2 API data access
Introduced a new TeamsRepository class to handle database operations for the v2 Teams API. This component provides methods for creating, reading, updating, and deleting teams, as well as retrieving team membership details (including platform-managed users) and finding teams by slug. It also includes logic to set a default conferencing application for a team by updating the team's metadata.
apps/api/v2/src/modules/teams/teams · high confidence
Added availability troubleshoot page with error handling and loading states
A new troubleshoot page has been added to the availability section, featuring a layout that wraps content in an ErrorBoundary for resilience and a Suspense boundary with a LoaderIcon fallback to handle loading states. The page itself is implemented as a server component that renders the client-side troubleshoot view, ensuring proper separation of concerns within the App Router structure.
apps/web/app/(use-page-wrapper)/availability/troubleshoot · high confidence
Added credential sync integration helpers for Google Calendar and Zoom
The credential-sync example app now includes a new \lib/integrations.ts\ module that provides functions to generate access tokens for Google Calendar and Zoom services. This addition enables the example application to programmatically refresh OAuth tokens for these third-party integrations, supporting the credential synchronization workflow.
example-apps/credential-sync · high confidence
Added stubbed NoSlotsNotificationService in slots feature
The slots feature now includes a new \NoSlotsNotificationService\ class and its corresponding test suite. The implementation currently provides a no-op \handleNotificationWhenNoSlots\ method that returns immediately without sending notifications, and the tests verify this behavior across various input scenarios (missing team ID, null org domain, multiple events). This appears to be a structural addition or placeholder for future notification logic rather than an active behavioral change for end-users at this stage.
packages/features/slots · high confidence
Added webhook API routes for Alby and PayPal integrations
New API endpoint files have been added for the Alby and PayPal integrations. These routes act as proxies, re-exporting the default webhook handlers from the respective app-store modules while disabling the body parser to handle raw webhook payloads correctly.
apps/web/pages/api/integrations/paypal · high confidence
Admin apps settings page now displays a categorized list
The admin settings area now includes a dedicated page for managing apps by category. This new route renders a header and an \AdminAppsList\ component, which presents the available applications in a scrollable navigation layout. Additionally, a basic admin index page has been added to serve as the root for the admin settings section.
apps/web/app/(use-page-wrapper)/settings/(admin-layout)/admin/apps/\[category\] · high confidence
Alby Lightning Network payment integration
Users can now accept Lightning Network payments for bookings via the Alby app. The new Setup page allows users to connect their Alby account and configure webhooks, while the Payment Component provides a user interface to pay via the WebLN browser extension or by scanning a QR code, with automatic booking status updates upon successful payment.
apps/web/components/apps/alby · high confidence
App Router migration infrastructure and theme handling
This change introduces the core library utilities required for the Next.js App Router migration. It adds \app-providers-app-dir.tsx\ and \app-providers.tsx\ to manage application-level providers (theme, feature flags, i18n) for the App and Pages routers respectively, alongside \buildLegacyCtx.ts\ to bridge App Router contexts to legacy Pages Router expectations. It also implements \getThemeProviderProps.ts\ to solve theme flickering in embeds and booking pages by generating unique \localStorage\ storage keys, and adds \buildNonce.ts\ with CSP support for security compliance.
apps/web/lib · high confidence
Automated synchronization of app metadata and validation of required keys
A new cron API endpoint at /api/cron/syncAppMeta has been added to ensure that application metadata stored in the database remains synchronized with the current app configuration files. This endpoint automatically updates app categories and directory names in the database to match their source definitions. Additionally, it enforces that apps are only enabled if they possess valid required keys; apps missing these keys are automatically disabled, with a warning logged to alert administrators to configure the necessary settings.
apps/web/app/api/cron/syncAppMeta · high confidence
BTCPay Server webhook API route added
A new API route at /api/integrations/btcpayserver/webhook has been introduced to handle incoming webhooks from BTCPay Server. This route acts as a proxy, re-exporting the default handler from the @calcom/app-store/btcpayserver package and is configured with the body parser disabled to ensure raw payload processing.
apps/web/pages/api/integrations/btcpayserver · high confidence
BotID integration for team event bookings
The bot-detection feature now integrates with the BotID service to verify human users during the booking flow for team events. When the instance-level BotID feature is enabled, the system validates the event type ID and checks if the associated team has the 'booker-botid' feature flag active. If a bot is detected, the booking request is blocked with a 403 Access denied error; otherwise, the request proceeds. This change also includes input validation to reject invalid event type IDs with a 400 Bad Request error.
packages/features/bot-detection · high confidence
Browser push notifications with optional VAPID configuration
The application now supports sending browser push notifications via the Web Push protocol. This feature allows users to receive instant meeting alerts and other notifications directly in their browser. The implementation uses VAPID keys for authentication but is designed to be resilient: if the required environment variables (NEXT\_PUBLIC\_VAPID\_PUBLIC\_KEY and VAPID\_PRIVATE\_KEY) are not set, the system logs a warning and disables push notifications rather than failing to initialize, ensuring the API remains stable even without push configuration.
packages/features/notifications · high confidence
Cal Video now supports automatic recording and transcription
Cal Video now offers automatic recording and transcription features for meeting organizers. When enabled, these actions start automatically upon joining a meeting, with the recording defaulting to a 2000 kbps bitrate. The UI includes dedicated tray buttons for managing these features, displaying clear states (Start, Stop, Waiting) and icons for both recording and transcription activities.
apps/web/modules/videos · high confidence
Centralized API route for app integrations
A new catch-all API route at \/api/integrations/\[...args\]\ has been introduced to handle integration actions. This route dynamically loads handlers from the app store based on the app name and endpoint (such as 'add'), managing authentication, team access validation, and credential creation. It provides a unified entry point for installing and configuring third-party apps, including support for redirect URLs after installation.
apps/web/pages/api/integrations · high confidence
Centralized TypeScript type definitions for the application
The \packages/types\ directory now contains a comprehensive set of TypeScript declaration files that define the core data models and interfaces used across the platform. This includes schemas for App metadata (including paid app data and location types), Calendar and CRM services, Video API adapters, Payment services, and User/Session structures. It also introduces validation schemas via Zod for app metadata and provides type definitions for environment variables, Next.js routing, and UI components like data tables and date pickers, ensuring consistent typing for these areas throughout the codebase.
packages/types · high confidence
Conferencing repository now supports team-level app queries
The new ConferencingRepository introduces methods to retrieve conferencing application credentials for both individual users and teams. Specifically, it adds findTeamConferencingApps and findTeamConferencingApp, enabling conferencing apps to be installed and queried at the team level in addition to the existing user-level lookups. The repository also standardizes credential selection using the TypeScript \satisfies\ operator and explicitly excludes sensitive fields like \credential.key\ from API outputs.
apps/api/v2/src/modules/conferencing/repositories · high confidence
Consolidated dayjs package with custom business-days plugin
The dayjs library is now centralized in a single package that pre-configures essential plugins (UTC, timezone, relative time, etc.) and includes a new custom 'business-days-plugin'. This plugin adds methods to calculate business days, check for holidays, and manage working weekdays, enabling more accurate scheduling logic for users dealing with business calendars.
packages/dayjs · high confidence
Defined response DTOs for OAuth client creation and retrieval
Added specific response Data Transfer Objects for the OAuth clients API: \CreateOAuthClientResponseDto\ (handling success/error statuses and client data, plus a redirect variant), \GetOAuthClientResponseDto\ (single client details), and \GetOAuthClientsResponseDto\ (list of clients). These DTOs standardize the API response structure for creating and fetching OAuth clients, ensuring consistent status reporting and data validation via Swagger decorators and class-validator rules.
apps/api/v2/src/modules/oauth-clients/controllers/oauth-clients/responses · high confidence
Display decoy booking confirmation for spam protection
Users who trigger the new async spam check via a decoy booking now see a dedicated success page instead of a standard confirmation. This new route renders the DecoyBookingSuccessCard, which displays the booking title, formatted date and time (adjusted to the booker's or host's time zone), host name, and attendee details, while explicitly omitting the host email for security.
apps/web/app/(booking-page-wrapper)/booking-successful · high confidence
Embed generator adds React (Atom) option and fixes namespace handling
The embed code generator now includes a new "React (Atom)" tab that provides code snippets using the \@calcom/atoms\ package and the \BookerEmbed\ component, alongside the existing HTML and React (iframe) options. The generator also fixes namespace handling in React snippets by correctly using bracket notation for invalid variable names (e.g., those with hyphens) and ensures the \calOrigin\ property is passed for self-hosted or organization embeds where required.
packages/features/embed · high confidence
Expanded language support with new and updated translations
The i18n package now includes complete translation sets for several new languages, specifically Arabic, Azerbaijani, Bulgarian, Bengali, and Catalan, making the application accessible to a wider global audience. Additionally, existing translations for other supported languages have been updated to fix typos, correct formatting issues (such as missing spaces in Hebrew and Japanese), and improve overall accuracy.
packages/i18n · high confidence
Implement server-side props for the new app installation flow
The app installation interface now uses a dedicated \getServerSideProps\ file to fetch and prepare data on the server. This change introduces logic to retrieve user-administered teams (including organization hierarchy), map event types with their specific settings (such as booking fields and locations), and identify available apps. It also adds support for fetching sub-teams within organizations, laying the groundwork for team-level app installation capabilities.
apps/web/lib/apps/installation · high confidence
Initial deployment module with license check stub
The API v2 now includes a new Deployments module that wires up the repository, service, and Redis integration for deployment data access. The service currently provides a checkLicense method that always returns true, effectively bypassing license validation for the time being.
apps/api/v2/src/modules/deployments · high confidence
Introduce @calcom/atoms as a standalone npm package for platform integration
The \packages/platform/atoms\ directory is now published as a standalone npm package (\@calcom/atoms\), providing customizable UI components (such as the Booker, AvailabilitySettings, and BookerEmbed) to integrate scheduling into external services. This release includes the \CalProvider\ for authentication and configuration, a new \BookerEmbed\ component for iframe-based embedding, and a local Stripe setup guide (\STRIPE.md\) for testing platform billing subscriptions. The package supports React 18/19 and Next.js 14/15, and uses changesets for versioning and changelog management.
packages/platform · high confidence
Introduce @coss/ui component library based on Base UI
The packages/coss-ui location now provides a new shared UI component library built on Base UI, replacing the previous Radix UI foundation. This includes the core component implementations (such as Accordion, AlertDialog, Alert, Avatar, Badge, Button, Card, Checkbox, and Combobox) which utilize Base UI primitives and a \render\ prop pattern for composition instead of Radix's \asChild\. The package also includes configuration files (components.json) and comprehensive migration guides to help developers transition existing Radix/shadcn-based components to the new Base UI mental model, addressing API differences like \\*Content\ to \\*Popup\/\\*Panel\ renames and specific behavioral quirks like portal interactions.
packages/coss-ui · high confidence
Introduce Booking Audit System foundation with DI and action services
This change establishes the core Booking Audit System in the \packages/features/booking-audit\ directory, providing an immutable, append-only trail for all booking-related actions. It introduces a dependency injection (DI) layer that wires up repositories (e.g., \PrismaAuditActorRepository\, \PrismaBookingAuditRepository\) and services (e.g., \BookingAuditViewerService\, \BookingHistoryViewerService\, \BookingAuditTaskConsumer\) using a modular token-based system. The system tracks specific booking events—including CREATED, ACCEPTED, CANCELLED, RESCHEDULED, ATTENDEE\_ADDED/REMOVED, LOCATION\_CHANGED, and NO\_SHOW\_UPDATED—via dedicated action services (\\*AuditActionService\) that enforce per-action schema versioning and handle data enrichment. This infrastructure ensures that audit records persist independently of user or booking deletions, supporting compliance and historical preservation.
packages/features/booking-audit · high confidence
Introduce CreditsRepository for centralized credit balance data access
A new \CreditsRepository\ class has been added to the credits feature to centralize all database interactions related to credit balances. This repository provides methods to retrieve credit balances for users or teams, including detailed views that join team or user information and filter expense logs by date range and credit type. By encapsulating these Prisma queries, the credits feature now has a dedicated, testable layer for managing credit data, improving code organization and maintainability.
packages/features/credits · high confidence
Introduce Dub-powered referral program page
The referral page now uses the Dub embed component to display the referral program when the IS\_DUB\_REFERRALS\_ENABLED flag is active, replacing the previous static placeholder with a dynamic interface that fetches a user-specific token and respects the system theme. A loading skeleton state is also provided to improve perceived performance while the token is being retrieved.
apps/web/app/(use-page-wrapper)/refer · high confidence
Introduce OrganizationsModule for API v2
The API v2 organizations module is now established as a distinct NestJS module, wiring together core dependencies such as Prisma, Stripe, Redis, Email, and Users, along with specific v2 sub-modules for event types, private links, and schedules. This change consolidates the service and repository providers (including OAuth client, conferencing, and OOO services) required to support the new organization-centric endpoints in the v2 API layer.
apps/api/v2/src/modules/organizations · high confidence
Introduce structured feature opt-in system with auto-opt-in and policy-based state resolution
This change introduces a new feature opt-in framework that allows features to be enabled at the organization, team, or user level. It adds a configuration system (config.ts) to define opt-in features, including display locations (settings vs. banner) and Formbricks feedback surveys. The core logic (FeatureOptInService, computeEffectiveState) implements a hierarchical state resolution with 'permissive' and 'strict' policies, determining if a feature is effectively enabled based on global, org, team, and user states. It also introduces auto-opt-in capabilities (applyAutoOptIn) that can automatically enable features for users/teams/orgs if they are in an 'inherit' state and auto-opt-in is enabled at that level. The system includes DI tokens and service interfaces to manage these states.
packages/features/feature-opt-in · high confidence
Introduce typed Redis service with Upstash integration and DI wiring
Users now have a strongly-typed Redis abstraction (IRedisService) that wraps the Upstash Redis client, supporting standard operations like get, set with TTL, expire, list range, and delete. A NoopRedisService is provided as a fallback when environment variables are missing, ensuring the application remains stable in testing or misconfigured environments. The service is wired into the dependency injection container via redisModule, which automatically selects the real Upstash client when UPSTASH\_REDIS\_REST\_URL and UPSTASH\_REDIS\_REST\_TOKEN are present, or the no-op implementation otherwise.
packages/features/redis · high confidence
Introduce v2 API memberships module
This change adds the foundational data access layer for the v2 API memberships module. It introduces a new NestJS module that wires together a Prisma-based repository and a service layer. The repository implements specific database queries for managing organization memberships, including finding users by team ID, identifying platform owners and admins, and checking administrative privileges. The service layer adds business logic to determine shared memberships between users and verify if one user holds admin or owner roles within organizations where another user is a member.
apps/api/v2/src/modules/memberships · high confidence
Introduce v2 Atoms module with email verification and secondary email management
The new Atoms module in the v2 API adds support for managing secondary emails and handling email verification flows. Users can now retrieve verified secondary emails, check for existing secondary email records, and add new verified secondary emails via the \AtomsSecondaryEmailsRepository\. Additionally, the module introduces endpoints for sending verification emails and verifying email codes, supporting the Booker atom's email verification requirement. The module also includes repositories for retrieving user teams and payment data, and registers controllers for event types, conferencing apps, schedules, and verification.
apps/api/v2/src/modules/atoms · high confidence
Introduce v2 OAuth client management module
The API v2 now includes a dedicated OAuth client module that provides the backend infrastructure for managing platform OAuth clients. This change adds the \OAuthClientModule\ NestJS module along with its repository and service layer, enabling the creation, retrieval, updating, and deletion of OAuth clients associated with organizations, teams, and users. It also introduces logic to fetch OAuth client parameters from event-type hosts, supporting the platform's managed user and organization workflows.
apps/api/v2/src/modules/oauth-clients · high confidence
Introduces App Dependency UI and Context for App Store
The App Store now supports declaring and displaying app dependencies. A new \AppDependencyComponent\ renders a status banner in the app store listing, showing which required apps are connected and providing direct links to install any missing dependencies. The \getAppRegistryWithCredentials\ backend function now resolves these dependencies and attaches the data to the app registry. Additionally, a new \EventTypeAppContext\ and \EventTypeAppCard\ component provide a typed context for event-type apps to access and modify their configuration data, while the \DynamicComponent\ utility enables dynamic rendering of app-specific settings and cards based on the app slug.
packages/app-store · high confidence
Introduces App Router infrastructure and layout for the web application
This change establishes the foundational structure for the Next.js App Router within the \apps/web/app\ directory. It adds a new \layout.tsx\ that serves as the root layout, handling internationalization via \AppRouterI18nProvider\, font configuration, and embedding logic. The update includes new error boundaries (\error.tsx\, \global-error.tsx\) that capture and report errors to Sentry, a \not-found.tsx\ page with client-side logic for handling 404 states, and a root \page.tsx\ that manages session-based redirects to login or onboarding flows. Additionally, it introduces utility components and wrappers such as \WithEmbedSSR\ for handling server-side rendering in embeds, \SpeculationRules\ for performance optimization, and context providers for geolocation and i18n.
apps/web/app · high confidence
Introduces Onboarding v3 with new UI components and flows
The onboarding experience has been redesigned with a new v3 interface. This update introduces a suite of reusable UI components including OnboardingLayout, OnboardingCard, and browser-view simulations for profile, calendar, and invite steps. The flow now supports personal, team, and organization onboarding paths, featuring new capabilities such as email-based team invites with role selection, member migration visualization, and a continuation prompt to guide users through the setup process.
apps/web/modules/onboarding · high confidence
Introduces Tasker, a background task execution system
Adds the Tasker package, a new pattern for offloading non-critical background tasks such as sending webhooks, creating CRM events, and processing analytics. It provides a pluggable architecture with a default \InternalTasker\ backed by the database, supporting scheduled execution, automatic retries with configurable intervals, and task cancellation. The system includes specific handlers for booking audits, no-show detection, and payment reminders, along with API routes to trigger task processing and cleanup via cron jobs.
packages/features/tasker · high confidence
Introduces a safe HTML description component for event types
A new component, EventTypeDescriptionSafeHTML, has been added to render event type descriptions as sanitized HTML. This component accepts an event type object containing both a plain text description and a pre-sanitized HTML version (descriptionAsSafeHTML), ensuring that rich text content is displayed safely without exposing the application to cross-site scripting risks.
apps/web/components/eventtype · high confidence
Introduces dedicated Profiles module with read/write service separation
A new ProfilesModule and ProfilesRepository have been added to the API v2 application. The repository implements profile management operations (creating, updating, and retrieving platform owner user IDs) and explicitly separates database access by injecting both PrismaReadService and PrismaWriteService, ensuring that write operations are routed through the dedicated write service while reads use the read service.
apps/api/v2/src/modules/profiles · high confidence
Introduces structured watchlist and booking report management capabilities
This change introduces a new, structured backend for managing watchlists and booking reports, replacing ad-hoc logic with a dedicated feature module. For watchlists, it adds a facade-based service layer (\WatchlistFeature\) that separates global and organization-specific blocking, includes a free email domain checker (identifying domains like Gmail/Outlook or those in the watchlist), and provides DTOs and mappers for API responses. For booking reports, it adds a new \IBookingReportRepository\ interface and \PrismaBookingReportRepository\ implementation, enabling admins to list, group, and filter reported bookings (including linking them to watchlist entries) and update their status. The change also adds comprehensive tests for the new repositories and services.
packages/features/watchlist · high confidence
Introduces the Troubleshooter atom with state management and UI components
This change adds the foundational structure for the Troubleshooter feature, including a Zustand store for managing event selection, date navigation, and calendar color mapping, alongside new UI components for displaying event type selectors, calendar connection statuses, and schedule items.
packages/features/troubleshooter · high confidence
Introduction of API v2 as a standalone Nest.js service
A new API v2 implementation is introduced as a standalone Nest.js application located in \apps/api/v2\. This service includes its own Dockerfile, environment configuration, and dependency management, running on a separate port (default 5555) from the existing API. It features custom API versioning via the \Cal.com-API-Version\ header, a dedicated rate-limiting strategy using Redis, and specific exception filters for handling Prisma, TRPC, and HTTP errors. A proxy entry point in \apps/api/index.js\ routes traffic to this new service under the \/v2\ path, while the legacy API remains accessible at the root path.
apps/api · high confidence
Introduction of API v2 authentication module
The API v2 now includes a dedicated authentication module that configures both Next.js and API key-based authentication strategies. This module integrates with existing services for users, memberships, tokens, deployments, and Redis, exposing guards for both authentication methods to secure API endpoints.
apps/api/v2/src/modules/auth · high confidence
Introduction of CalVideoSettingsRepository for data persistence
A new CalVideoSettingsRepository has been added to the calVideoSettings feature package to centralize database operations for Cal Video settings. This repository provides static methods to create, update, or delete settings records (such as recording and transcription preferences) for specific event types via Prisma, establishing a dedicated data-access layer for this feature.
packages/features/calVideoSettings · high confidence
Introduction of Kysely database client package
A new \packages/kysely\ module has been added to provide a Kysely-based database client. This package exports a configured \Kysely\ instance connected to a PostgreSQL database via \pg\, utilizing \ParseJSONResultsPlugin\ and \DeduplicateJoinsPlugin\. It also includes a \traverseJSON\ utility function for navigating JSON columns and re-exports the \DB\ and \Booking\ type definitions.
packages/kysely · high confidence
Introduction of Kysely database services for read and write operations
The API v2 module now includes dedicated Kysely services for database interactions, separating read and write connections. The new KyselyReadService and KyselyWriteService initialize Kysely instances using separate PostgreSQL connection pools configured via 'db.readUrl' and 'db.writeUrl' respectively, and export these services through the KyselyModule for dependency injection.
apps/api/v2/src/modules/kysely · high confidence
Introduction of Selected Calendars Service
A new SelectedCalendarsService has been added to the API v2 module to manage user-selected calendar associations. This service provides methods to add and delete selected calendars, handling credential validation via the CalendarsService, persisting changes through the repository, and invalidating the relevant calendar caches. It also implements specific error handling for deletion operations, mapping internal errors to appropriate HTTP exceptions (NotFound, BadRequest, InternalServerError).
apps/api/v2/src/modules/selected-calendars/services · high confidence
Introduction of dedicated JWT module and service in API v2
The API v2 now includes a dedicated JWT module that configures the NestJS JWT provider using an environment variable for the secret and exports a custom JwtService. This service provides specific methods for signing access and refresh tokens, ensuring tokens include an issued-at timestamp in seconds, and allows decoding of existing tokens.
apps/api/v2/src/modules/jwt · high confidence
Introduction of destination calendar module with domain-wide delegation support
The API v2 now includes a dedicated destination-calendars module that manages calendar integration settings. This module introduces support for domain-wide delegation credentials (delegationCredentialId) alongside standard credentials, allowing for more flexible calendar synchronization. The implementation includes a new NestJS module wiring the necessary repositories and services, backed by Prisma for data persistence and Redis for caching, enabling users to configure destination calendars with delegated access capabilities.
apps/api/v2/src/modules/destination-calendars · high confidence
New /api/me endpoint with performance timing and 401 on unauthenticated access
The application now exposes a new GET /api/me route that returns the current user's name along with detailed performance metrics (Prisma, session, and user lookup durations). For unauthenticated requests, the endpoint explicitly returns a 401 Unauthorized status, correcting previous behavior that may have returned 409 Conflict. The implementation uses a legacy request builder for compatibility and wraps the handler with a standard app-dir responder.
apps/web/app/api/me · high confidence
New API authentication strategy for v2 API
The v2 API now uses a dedicated \ApiAuthStrategy\ to handle authentication, supporting multiple methods including API keys, OAuth client credentials, access tokens, and NextAuth tokens. This strategy validates credentials via specific headers (\X-CAL-CLIENT-ID\, \X-CAL-SECRET\_KEY\) or Bearer tokens, correctly associating requests with their respective organizations and users. It also includes logic to handle third-party access tokens and provides clear error messages when authentication headers are missing or incomplete.
apps/api/v2/src/modules/auth/strategies/api-auth · high confidence
New API endpoint for checking username availability
A new API route at /api/username has been added to allow clients to check if a desired username is available. The endpoint accepts a POST request with a JSON body containing the username and an optional organization slug, validates the input using Zod, and returns the availability result from the core profile logic. It also includes error handling to return a 400 status if the check fails.
apps/web/app/api/username · high confidence
New API endpoint for generating Dub referral tokens
A new API route at /api/user/referrals-token has been added to support the Dub referral integration. This endpoint allows authenticated users to request a public referral token by calling the Dub embed API, provided the feature is enabled via configuration. The response includes the generated public token, which can be used for embedding referral links.
apps/web/app/api/user · high confidence
New API endpoint for serving team-specific logos and favicons
A new API route at \/api/logo\ has been introduced to dynamically serve branding assets (logos, favicons, touch icons) based on the request's hostname subdomain. This endpoint resolves custom team logos from the database, falling back to default Cal.com assets if no custom branding is found or if the subdomain is a system domain. It includes SSRF protection to validate image URLs and supports various icon types (e.g., favicon-16, apple-touch-icon) via query parameters.
apps/web/app/api/logo · high confidence
New API endpoints for guest video sessions and recording downloads
This change introduces two new API routes in the video application area. The \/api/video/guest-session\ endpoint allows guests to obtain a meeting password and URL for Cal Video bookings by validating their email against the booking participants and enforcing CSRF protection; it also handles token expiration updates (set to 14 days after the booking end time). The \/api/video/recording\ endpoint provides a secure way to download video recordings by verifying a signed token and redirecting the user to the actual download link, with appropriate error handling for missing tokens, invalid/expired tokens, and missing recordings.
apps/web/app/api/video · high confidence
New API endpoints for regular and recurring bookings
The booking API surface in apps/web/pages/api/book has been expanded with two new entry points: event.ts for single bookings and recurring-event.ts for recurring bookings. Both endpoints now enforce Cloudflare Turnstile bot detection (when enabled), apply core rate limiting using hashed IP identifiers, and delegate the actual booking creation to dedicated services (RegularBookingService and RecurringBookingService) while recording the creation source as WEBAPP. A corresponding test suite for recurring-event.ts validates multi-slot creation, calendar/webhook/email side effects, and error handling.
apps/web/pages/api/book · high confidence
New API endpoints to manage selected calendars
The API v2 now exposes endpoints to add and remove selected calendars for a user. Users can POST to /v2/selected-calendars to add a calendar integration (specifying the integration type, external ID, and credential ID) and DELETE from the same path to remove a selected calendar by providing the relevant query parameters. These endpoints are protected by API authentication and return a standardized success response containing the calendar details.
apps/api/v2/src/modules/selected-calendars/controllers · high confidence
New API key management UI and backend security infrastructure
Users can now create, edit, and delete API keys with custom expiration dates (7 days, 30 days, 3 months, 1 year, or never) and personal notes via a new web interface. The system introduces automatic account locking for users who repeatedly exceed rate limits, using Redis to track failures and Prisma to enforce the lock. API keys are now securely stored as SHA-256 hashes, and the backend provides a structured service layer for key verification and generation.
apps/api/v2/src/modules/teams/event-types/pipes, apps/web/modules/api-keys, packages/features/api-keys-legacy · high confidence
New API routes for Daily Video webhooks and HelpScout integration
This change introduces two new API routes in the App Router structure. The \recorded-daily-video\ route handles Daily Video webhooks, processing events such as recording readiness (triggering email notifications and transcription jobs) and meeting endings (sending transcript emails), while validating incoming requests via HMAC signatures. The \sync/helpscout\ route allows HelpScout to securely retrieve user profile information (username, account creation date, and last booking date) by verifying an HMAC signature against the request body.
apps/web/app/api/recorded-daily-video · high confidence
New API v2 OAuth flow endpoints for authorization, token exchange, and refresh
The API v2 now exposes a dedicated OAuth flow controller at \/v2/oauth/:clientId\ with three new endpoints: \POST /authorize\ to initiate the authorization code grant (requiring user authentication and validating redirect URIs), \POST /exchange\ to swap the authorization code for access and refresh tokens (returning \accessToken\, \refreshToken\, and their expiration timestamps), and \POST /refresh\ to rotate and obtain new tokens using the client secret and a valid refresh token. These endpoints are part of the deprecated Platform/Managed Users feature set, as indicated by the Swagger tags, and include comprehensive end-to-end tests verifying authentication requirements, token structure, and expiration handling.
apps/api/v2/src/modules/oauth-clients/controllers/oauth-flow · high confidence
New API v2 Users module with platform-managed user support
A new UsersModule has been introduced in the API v2 stack, wiring together the UsersService, UsersRepository, PrismaModule, EventTypesModule, and TokensModule. The repository layer now explicitly supports platform-managed users by setting the \isPlatformManaged\ flag and recording \creationSource\ as \API\_V2\ during user creation. It also provides scoped lookup methods like \findByIdWithinPlatformScope\ to ensure platform clients only access users they own, and enriches user queries with profile and organization data (including \isPlatform\ status) for better context in the dashboard and API responses.
apps/api/v2/src/modules/users · high confidence
New API v2 selected-calendars module with delegation credential support
This change introduces the API v2 module for managing user-selected calendars, providing the input/output DTOs, service, repository, and NestJS module wiring. Users can now interact with selected calendars via the v2 API, which supports upserting, retrieving, and removing calendar selections. A key capability is the support for delegation credentials: the input DTOs and repository methods accept an optional delegationCredentialId, allowing the system to manage calendar selections associated with domain-wide delegation credentials in addition to standard user credentials.
apps/api/v2/src/modules/selected-calendars · high confidence
New App Store UI components and calendar settings wrappers
This change introduces a new set of React components in \apps/web/components/apps\ to power the App Store and calendar management interfaces. Key additions include \App.tsx\ and \AppPage.tsx\ for rendering individual app detail pages with installation logic, \InstallAppButtonChild.tsx\ for handling install/disconnect states (including support for paid apps and multi-install scenarios), and \MultiDisconnectIntegration.tsx\ for managing multiple credentials. It also adds \CalendarListContainer.tsx\ and \DestinationCalendarSettingsWebWrapper.tsx\ to display connected calendars and configure destination calendar settings with reminders. Additionally, \AppSetupPage.tsx\ provides a dynamic map for app-specific setup screens (e.g., ICS Feed, Stripe), and \ics-feedcalendar/Setup.tsx\ implements the UI for adding ICS feed URLs.
apps/web/components/apps · high confidence
New Apps module with repository for managing app credentials
A new Apps module has been introduced in the API v2, providing the foundational repository layer for managing application integrations. This includes the ability to retrieve apps by slug and manage credentials for both individual users and teams, supporting creation and deletion of app-specific credentials via the Prisma database service.
apps/api/v2/src/modules/apps · high confidence
New Atom services for conferencing, event types, schedules, and email verification
This change introduces four new service classes in the v2 API atoms module to support the new Atom-based user interface components. The \ConferencingAtomsService\ retrieves installed conferencing apps for a user, while the \EventTypesAtomService\ handles fetching, updating, and validating event types with specific logic for team ownership and date normalization. The \SchedulesAtomsService\ manages schedule retrieval and updates, and the \VerificationAtomsService\ implements the send and verify code flow for email verification, including handling of secondary emails and OAuth client ID stripping.
apps/api/v2/src/modules/atoms/services · high confidence
New BTCPay Server and HitPay payment integration components
Added new React components for the BTCPay Server and HitPay payment apps. The BTCPay component (\BtcpayPaymentComponent\) renders an iframe for the checkout page and polls for payment status to redirect users upon success, while the setup page (\Setup.tsx\) handles API key configuration and automatic webhook registration. Similarly, the HitPay components (\HitpayPaymentComponent\ and \Setup.tsx\) provide a drop-in payment interface and a setup form for managing API keys and sandbox modes.
apps/web/components/apps/btcpayserver · high confidence
New Booker Atom with Zustand state management and assignment reason tracking
The booking interface has been refactored into a new 'Booker' atom located in \packages/features/bookings/Booker\. This introduces a dedicated Zustand store (\store.ts\, \BookerStoreProvider.tsx\) to manage booking state (dates, times, form values) and a new \AssignmentReasonRepository\ to persist routing assignment reasons. The new component supports multiple layouts (month, week, column, mobile), handles slot reservation logic to prevent double-bookings, and includes hooks for layout validation and timezone handling.
packages/features/bookings · high confidence
New Booking History component with advanced filtering and i18n support
The BookingHistory component has been introduced to display detailed audit logs for bookings, featuring search and actor filtering capabilities. It now supports complex display fields including translations with parameters and embedded links, ensuring proper internationalization. The component also utilizes date-fns for consistent timestamp formatting and provides a structured view of audit actions with actor details and JSON data viewers.
apps/web/modules/booking-audit · high confidence
New CRM Manager and Scheduler components
This change introduces a new CrmManager class and a CRMScheduler utility within the CRM Manager feature. The CrmManager class provides a unified interface for interacting with CRM services, handling operations such as creating, updating, and deleting events, as well as managing contacts and attendee no-shows. It includes logic to check for existing contacts, create new ones if necessary, and delegate specific actions to the underlying CRM service. The CRMScheduler component facilitates the asynchronous creation of CRM events via a task queue, allowing for configurable retry attempts. Additionally, a test file is added to cover the CrmManager's functionality, including mocking CRM services and testing event creation scenarios.
packages/features/crmManager · high confidence
New Calendar Cache and Sync feature for Google and Office 365
This location introduces the implementation for the Calendar Cache and Sync feature, providing efficient calendar synchronization with intelligent caching to reduce API calls and ensure real-time updates. It includes a provider-agnostic adapter system with specific implementations for Google Calendar and Office 365, handling webhook subscriptions, event fetching (including incremental sync via delta links/sync tokens), and webhook validation. The feature relies on a new \CalendarCacheEvent\ database table to store cached busy events and is controlled by two feature flags: \calendar-subscription-cache\ (for caching) and \calendar-subscription-sync\ (for webhook-based real-time sync), which can be enabled globally, per team, or per user.
packages/features/calendar-subscription · high confidence
New Connect and Join view for instant bookings
A new client-side view component has been added to the connect-and-join module, enabling users to join an instant meeting via a token. The interface handles session loading states, validates the presence of a token, and provides a 'Join Meeting' button that triggers a tRPC mutation. If the user is not part of an organization, the button is disabled with an appropriate tooltip. Upon successful mutation, the user is redirected to the meeting URL; if another host has already accepted the booking, the view displays a link to continue to the meeting instead. Error states are handled by displaying an alert with the specific tRPC error message or a generic failure message.
apps/web/modules/connect-and-join · high confidence
New DataTable system with filter segments and timezone handling
The data-table package now includes a comprehensive DataTable system featuring a segment mechanism for saving and sharing filter configurations (user- and team-scoped), robust date range filtering with preset options (today, last 7/30 days, month/year-to-date, custom) that automatically recalculates relative dates, and timezone-aware date handling that preserves local wall-clock times across timezones. The system also provides server-side SQL and Prisma query builders for various filter types (text, number, single/multi-select, date range), URL query parameter serialization, and separator row support in tables.
packages/features/data-table · high confidence
New GetAuthMethod decorator for retrieving authentication method
A new NestJS parameter decorator, GetAuthMethod, has been added to the API v2 authentication module. This decorator allows controllers to easily access the specific authentication method used for the current request (e.g., API key, session) by extracting it from the request object. If the authentication method is not set, it throws an error, ensuring that the caller explicitly handles or expects a valid auth method.
apps/api/v2/src/modules/auth/decorators/methods · high confidence
New GetMembership decorator for extracting membership data in API routes
A new NestJS parameter decorator, GetMembership, has been added to the V2 API authentication module. This decorator allows route handlers to easily extract the authenticated user's organization membership details from the request context. It supports returning the full membership object, a specific field, or an array of specific fields, simplifying access to membership data within protected endpoints.
apps/api/v2/src/modules/auth/decorators/get-membership · high confidence
New GetOptionalUser decorator for flexible user data extraction
A new \GetOptionalUser\ parameter decorator has been added to the v2 API authentication module. This decorator allows controllers to optionally retrieve the authenticated user from the request context, returning \null\ if no user is present. It supports flexible data extraction by accepting either a specific user property key, an array of keys to return a subset of user data, or no argument to return the full user object.
apps/api/v2/src/modules/auth/decorators/get-optional-user · high confidence
New GetOrg decorator for accessing organization data in API v2
A new \GetOrg\ parameter decorator has been added to the API v2 authentication module. This decorator allows controllers to easily inject organization (\Team\) data from the request context, supporting both full object retrieval and selective property extraction based on provided keys.
apps/api/v2/src/modules/auth/decorators/get-org · high confidence
New GetTeam decorator for extracting team context in API v2
A new \GetTeam\ parameter decorator has been added to the API v2 authentication module. This decorator allows controllers to easily inject team data from the request context, supporting both full team object retrieval and selective property extraction via an array of keys. It throws an error if the team context is missing, ensuring that endpoints relying on team data fail fast when the context is invalid.
apps/api/v2/src/modules/auth/decorators/get-team · high confidence
New GetUser decorator for extracting authenticated user data
A new \GetUser\ parameter decorator has been added to the API v2 authentication module. This decorator allows controllers to easily inject the authenticated user object from the request context. It supports returning the full user object, a specific user property by key, or an object containing multiple specified properties, and throws an error if no user is found in the request.
apps/api/v2/src/modules/auth/decorators/get-user · high confidence
New IP diagnostic endpoint
A new API route at /api/ip has been added to the web application. This endpoint returns the visitor's IP address in a JSON response, serving as a diagnostic tool to verify IP resolution logic.
apps/web/app/api/ip · high confidence
New Make integration setup page with API key management
Users can now set up the Make (formerly Integromat) integration directly within the app. A new Setup page allows users to generate and copy API keys for their account and specific teams, with instructions on how to connect via the Make Invite Link. The interface handles loading states and displays an 'App Not Installed' message if the prerequisite is missing.
apps/web/components/apps/make · high confidence
New OAuth client administration page with approval workflow
Administrators can now manage OAuth clients via a dedicated settings page at /settings/admin/oauth. This new page enforces authentication, redirecting unauthenticated users to the login screen, and renders the OAuth clients admin view to support the approval workflow for client management.
apps/web/app/(use-page-wrapper)/settings/(admin-layout)/admin/oauth · high confidence
New OAuth client management service layer
This change introduces a new service layer for managing OAuth clients within the API v2 platform. It adds input and output transformation services to handle permission mapping (converting between string permission names and numeric bitmask values) and JWT-based secret generation for new clients. The main service provides CRUD operations (create, read, update, delete) for OAuth clients, integrating with the repository layer to persist client data and return standardized DTOs to the API consumer.
apps/api/v2/src/modules/oauth-clients/services/oauth-clients · high confidence
New OAuth2 API endpoints for API v2
The API v2 now exposes a dedicated OAuth2 module providing standard OAuth 2.0 endpoints. Users can retrieve OAuth client details via GET /api/v2/auth/oauth2/clients/:clientId and exchange authorization codes or refresh tokens for access tokens via POST /api/v2/auth/oauth2/token. The implementation supports both confidential clients (using client\_secret) and public clients (using PKCE code\_verifier), and includes a separate Atoms-specific endpoint for client lookup. The module also introduces input validation for authorization and token requests, along with specialized error handling for OAuth redirects and HTTP exceptions.
apps/api/v2/src/modules/auth/oauth2 · high confidence
New OAuth2 authorize page implementation
A new server component page has been added at /auth/oauth2/authorize to handle OAuth2 authorization requests. This page generates metadata for the route and renders the underlying authorization view component within a server-side wrapper, establishing the entry point for the OAuth2 authorization flow.
apps/web/app/(use-page-wrapper)/auth/oauth2 · high confidence
New Or authentication guard for flexible access control
Added a new Or guard in the auth module that allows combining multiple authentication guards with OR logic, granting access if any single guard succeeds. The implementation includes the guard logic, an index export, and comprehensive unit tests covering scenarios where guards pass, fail, or throw errors.
apps/api/v2/src/modules/auth/guards/or-guard · high confidence
New Out-of-Office settings page added
A new page has been added at /settings/my-account/out-of-office to manage out-of-office settings. This page renders the OutOfOfficeView component and provides metadata for the route.
apps/web/app/(use-page-wrapper)/settings/(settings-layout)/my-account/out-of-office · high confidence
New SMS notification system for attendees
A new SMS notification system has been introduced for attendees, featuring a centralized SMSManager and specific message templates for events such as scheduling, cancellations, declines, and rescheduling. This system restricts SMS delivery to phone-only bookings (identified by a phone number and an @sms.cal.com email address) and implements per-organizer rate limiting to manage message volume.
packages/sms · high confidence
New Tasker API routes with cache control
New API endpoints have been added at /api/tasks/cleanup and /api/tasks/cron to expose the tasker's cleanup and cron logic. These routes wrap the underlying handlers with a standard responder and, for the cron endpoint, explicitly disable caching (revalidate=0) to ensure fresh data is processed on each scheduled run.
apps/web/app/api/tasks · high confidence
New Troubleshooter interface for diagnosing availability conflicts
A new Troubleshooter module has been added to the web application, providing a dedicated UI to help users identify and resolve scheduling conflicts. The interface features a sidebar for selecting event types and viewing connected calendars, alongside a large calendar view that visualizes busy times, date overrides, and available time slots. This tool allows users to inspect their availability schedules and connected apps in a consolidated view to troubleshoot booking issues.
apps/web/modules/troubleshooter · high confidence
New TypeScript types for scheduling and SSR prop inference
The application now includes dedicated TypeScript type definitions to support scheduling logic and server-side rendering. A new \inferSSRProps\ utility type has been added to \apps/web/lib/types/inferSSRProps.ts\ to correctly infer props from Next.js \getServerSideProps\ functions. Additionally, \apps/web/lib/types/schedule.ts\ introduces types for time ranges, schedules, working hours, and travel schedules, providing a structured schema for managing user availability and timezone changes.
apps/web/lib/types · high confidence
New UI component library and design system
The \packages/ui\ directory has been restructured to introduce a comprehensive set of reusable UI components, including AddressInput, MultiEmail, Select, Alert, AppListCard, Avatar, Badge, Breadcrumb, and Button. This change establishes a new design system foundation, providing standardized styling and behavior for common interface elements across the application.
packages/ui · high confidence
New UI components for 2FA and backup code entry
Added two new React components, BackupCode.tsx and TwoFactor.tsx, to the authentication flow. The TwoFactor component provides a dedicated input interface for entering 6-digit TOTP codes, while the BackupCode component handles the entry of backup codes with appropriate validation constraints.
apps/web/components/auth · high confidence
New UI components for authentication, modals, and badge management
This update introduces five new UI components to the application's design system. AuthContainer provides a standardized layout for authentication flows with optional logo and loading states. LimitedBadges allows displaying a limited number of badges with a popover to reveal additional items, improving space efficiency in lists. LinkIconButton offers a consistent style for icon-based action buttons. ModalContainer wraps dialog content with responsive sizing and scrolling options. SettingInputContainer standardizes the layout for form inputs paired with labels and icons in settings pages.
apps/web/components/ui · high confidence
New UI components for home screen prompts, US-only analytics, and notification sounds
This change introduces several new client-side components in the web application. The AddToHomescreen component displays a dismissible banner prompting users to install the app when viewed in a browser, hiding it if the app is already in standalone mode. A new Google Tag Manager (GTM) implementation uses a geolocation hook to conditionally load analytics scripts only for users in the US, caching the result for 24 hours. Additionally, a NotificationSoundHandler component manages browser audio playback for push notifications, initializing the audio context on first user interaction and playing a ringtone for 7 seconds when triggered by service worker messages. The I18nLanguageHandler component provides a dedicated tRPC query for fetching locale data with batching disabled to ensure independent caching, while the Loader component is now deprecated in favor of custom skeletons.
apps/web/components · high confidence
New UI components for settings page structure and theming
This change introduces new React components within the settings feature to improve the user interface and layout. A new \SettingsHeader\ component provides a consistent header layout with optional back-button navigation and loading states, while \SectionBottomActions\ offers a standardized container for action buttons at the bottom of settings sections. Additionally, a \ThemeLabel\ component has been added to allow users to visually select and switch between light, dark, and system theme variants directly within the settings interface.
packages/features/settings · high confidence
New URL and user-state hooks for booking pages and file handling
The web application introduces several new React hooks in the \apps/web/lib/hooks\ directory to improve URL parameter management and user context. \useIsBookingPage\ and \useNuqsParams\ now detect booking-related routes and handle query parameter sorting (specifically prioritizing the 'uid' parameter) for bookings pages. \useRouterQuery\ and \useToggleQuery\ provide standardized ways to read and toggle search parameters using the new \useCompatSearchParams\ hook. Additionally, \useCurrentUserId\ simplifies accessing the current user's ID from the \useMeQuery\, and \useFileReader\ offers a reusable interface for reading file contents with loading and error states.
apps/web/lib/hooks · high confidence
New Webhooks Module for API v2
A new WebhooksModule has been introduced in the API v2 structure, providing the foundational infrastructure for managing webhooks across users, event types, and OAuth clients. This module registers dedicated controllers and services to handle webhook creation, retrieval, updates, and deletion, backed by a new repository that interacts with the Prisma database layer. It enables the system to store and manage webhook configurations specific to different entity scopes (user, event type, and platform OAuth client) within the v2 API.
apps/api/v2/src/modules/webhooks · high confidence
New admin SMS lock management and OAuth client approval workflows
The settings area now includes an admin view for managing SMS lock states, allowing administrators to lock or unlock SMS sending for specific users and teams via a dedicated table and action buttons. Additionally, a new admin OAuth clients page has been added, enabling administrators to review, approve, or reject pending OAuth client applications, while the existing developer OAuth clients view now supports submitting new clients for review and managing their lifecycle.
apps/web/modules/settings · high confidence
New admin and security settings pages added
This change introduces three new settings pages to the application: a 'Locked SMS' page for administrators, and 'Password' and 'Two-Factor Authentication' pages for general security settings. Each page is implemented as a new route component that renders a specific view (LockedSMSView, PasswordViewWrapper, TwoFactorAuthView) within a shared SettingsHeader, ensuring consistent layout and metadata generation across these new sections.
apps/web/app/(use-page-wrapper)/settings/(admin-layout)/admin/lockedSMS, apps/web/app/(use-page-wrapper)/settings/(settings-layout)/security · high confidence
New admin interface for managing feature flags
Administrators now have a dedicated view to manage feature flags, allowing them to toggle flags on or off and assign specific flags to individual teams. The new FlagListingView presents flags grouped by type, with each flag displaying a toggle switch for global enablement and a button to open an assignment sheet. The AssignFeatureSheet component enables admins to search for teams and toggle feature access for each team individually, with real-time updates and toast notifications for success or error states. The useFlags hook provides the current state of all flags to the application, falling back to a hardcoded default configuration if the server query is unavailable.
apps/web/modules/feature-flags · high confidence
New auth feature module with session, permission, and provider utilities
A new \packages/features/auth\ module has been introduced to centralize authentication logic. It includes a \PermissionContainer\ component for role-based UI rendering, a custom \getServerSession\ implementation with LRU caching, and a NextAuth adapter (\CalComAdapter\) for database operations. The module also provides utilities for identity provider mapping, locale detection, and OAuth authorization, alongside comprehensive test coverage for session handling and provider resolution.
packages/features/auth · high confidence
New blocklist management UI and enhanced booking page filters
This change introduces a dedicated blocklist management interface within the web application, adding components for viewing blocked entries, reviewing pending booking reports, and creating new blocklist entries (for emails or domains) with audit history and system-wide scope support. Simultaneously, the bookings page is enhanced with a new filter configuration that adds hidden filter columns for event type, team, member, attendee name, attendee email, date range, and booking UID, enabling more granular filtering capabilities for users managing their bookings.
apps/web/modules/bookings · high confidence
New booking actions dropdown component with centralized state management
This location introduces the \BookingActionsDropdown\ component and its supporting infrastructure (\BookingActionsStoreProvider\, \store.ts\, \bookingActions.ts\) to manage booking actions. The dropdown provides a unified interface for actions like confirm, reject, cancel, reschedule, reassign, and report, with visibility and disabled states determined by booking status (e.g., past, cancelled, rejected) and user role. It uses a Zustand store to manage the open/close state of various dialogs (cancel, reschedule, reassign, etc.) and integrates with tRPC mutations for backend operations. The component supports different contexts (list vs. details) to show/hide specific actions.
apps/web/components/booking/actions · high confidence
New booking audit log page
A new route at /booking/\[uid\]/logs has been added, providing a dedicated page to view the audit history for a specific booking. This page renders the BookingHistoryPage component, allowing users to inspect actions such as booking creation, and is currently implemented as a standalone route to facilitate testing before potential integration into the booking page sidebar.
apps/web/app/(use-page-wrapper)/(main-nav)/booking · high confidence
New booking confirmation and rejection UI components
The booking list now includes dedicated Accept and Reject buttons for unconfirmed bookings, powered by a new \useBookingConfirmation\ hook that handles the tRPC mutation and UI state. These components support confirming or rejecting entire recurring series when viewed in the 'Recurring' or 'Unconfirmed' tabs, and the reject flow requires a reason via a dialog. A new \CancelBooking\ component enforces cancellation reasons and internal note requirements, and displays warnings for no-show fees. The \BookingListItem\ has been updated to use these new action components and a \SkeletonLoader\ has been added to improve loading states.
apps/web/components/booking · high confidence
New booking confirmation link API route
A new API route at \apps/web/app/api/link\ has been introduced to handle booking acceptance and rejection via magic links. This endpoint decrypts the provided token, validates the action (accept/reject), and delegates the core logic to \confirmHandler\. It ensures that users are redirected to the correct booking page using the configured \WEBAPP\_URL\, which prevents issues with localhost redirects when the application is running behind a proxy. Comprehensive tests have been added to verify the redirect URL construction and error handling behavior.
apps/web/app/api/link · high confidence
New booking management dialogs for guests, cancellations, and reassignments
This change introduces a suite of new dialog components in the booking flow, including AddGuestsDialog for inviting additional attendees, CancelBookingDialog for handling cancellations with reason requirements, ChargeCardDialog for processing payments, EditLocationDialog for updating meeting details, ReassignDialog for transferring bookings to team members or round-robin hosts, RejectionReasonDialog for declining requests, ReportBookingDialog for flagging issues, RescheduleDialog for requesting time changes, and WrongAssignmentDialog for correcting routing errors. These dialogs provide a unified interface for users to manage bookings, handle payments, and resolve scheduling conflicts.
apps/web/components/dialog · high confidence
New booking page error boundary and error page component
The booking page now includes a dedicated error boundary that catches runtime errors during rendering and displays a user-friendly error page. This page shows the HTTP status code, a friendly message, and a 'Try again' button to reload the page. When debugging is enabled, it also displays detailed error information (message, name, stack, HTTP status, etc.) to assist support. The error page integrates with the Cal.com embed iframe for proper status reporting.
apps/web/components/error · high confidence
New booking token verification API route
A new API route at \apps/web/app/api/verify-booking-token\ has been added to handle booking confirmation and rejection actions triggered via email links. The route supports GET requests for accepting bookings and POST requests for rejecting them (with a reason), using a one-time password token to identify the booking. It validates the token, retrieves the associated user and booking details, and delegates the actual confirmation/rejection logic to the existing \confirmHandler\. Redirects are performed to the booking confirmation page with appropriate success or error messages, using the configured \WEBAPP\_URL\.
apps/web/app/api/verify-booking-token · high confidence
New booking-seat module with repository for seat data access
A new BookingSeatModule and BookingSeatRepository have been introduced in the API v2 booking-seat area. The repository provides database access methods to retrieve booking seat records by reference UID, including detailed nested data for the associated booking, attendees, user, and event type. This establishes the data-access layer for seat-related operations within the v2 API.
apps/api/v2/src/modules/booking-seat · high confidence
New build and release utility scripts for the web app
Added four new scripts to the web application to improve build-time quality and release management. The \check-missing-translations\ script automatically detects and fills in missing translation keys for locales by comparing them against the English template. The \copy-app-store-static\ script copies static assets from app-store packages to the public directory and generates SVG hashes for caching. The \create-sentry-release\ script automates the creation of Sentry releases, including commit association, debug ID injection, and source map uploading. Finally, \ts-check-changed-files\ runs TypeScript type checking only on files changed since the main branch to catch type errors early in development.
apps/web/scripts · high confidence
New caching decorators and booking no-show handling logic
This change introduces declarative caching decorators (@Memoize and @Unmemoize) in packages/features/cache, allowing methods to automatically cache results in Redis and invalidate those caches upon execution. It also adds a new CalendarEventBuilder class to construct calendar events from bookings, and implements the core logic for marking attendees and hosts as no-shows (handleMarkNoShow), including sending no-show data to external apps and updating the database.
packages/features · high confidence
New calendar subscription cache and sync endpoints
The application now exposes two new API endpoints to support calendar subscription caching and synchronization. The cron route at /api/cron/calendar-subscriptions allows the system to periodically check for new subscriptions, while the webhook route at /api/webhooks/calendar-subscription/\[provider\] processes incoming updates from Google and Office 365 calendars. Both endpoints respect feature flags to enable or disable the cache and sync capabilities independently, ensuring that users can opt into these performance and data consistency improvements.
apps/web/app/api/cron/calendar-subscriptions, apps/web/app/api/webhooks · high confidence
New calendars feature area with improved booking UI and sync infrastructure
This change introduces a new \packages/features/calendars\ module that consolidates calendar logic and UI components. For users, this brings an improved DatePicker in the booking flow that adapts its view based on the time of month and offers clearer messaging when no availability exists (explaining rolling or range period limits). It also includes a DestinationCalendarSelector for choosing where events are created. Under the hood, a new CalendarsTasker infrastructure (sync and trigger versions) and a refactored CalendarManager are added to handle calendar synchronization and event processing, including specific fixes for Zoho Calendar attendee handling.
packages/features/calendars · high confidence
New credential-sync example app for managing third-party tokens
Added a new Next.js example application in \example-apps/credential-sync\ that serves as a source of truth for Cal.diy app credentials. This tool allows users to generate and manage access tokens for Google Calendar and Zoom, and sync them to Cal.diy via a secure API endpoint. It includes a UI for testing valid and invalid token scenarios, along with the necessary configuration files and environment variable examples to set up the sync process.
example-apps · high confidence
New credentials repository and module for API v2
This change introduces the foundational data-access layer for credentials in the API v2 module. It adds a new \CredentialsModule\ that exports a \CredentialsRepository\, which handles all database interactions for user and team credentials via Prisma. The repository provides methods to upsert, find, and delete credentials, including specific support for encrypted keys and delegation information required by the unified calendar API.
apps/api/v2/src/modules/credentials · high confidence
New cron endpoint for pending booking confirmation reminders
A new API route at /api/cron/bookingReminder has been added to automatically send reminder emails to organizers for bookings that are still pending confirmation. The endpoint checks for bookings created 3, 24, and 48 hours ago that have not yet been confirmed or finished, ensuring reminders are only sent if the organizer has not already been notified for that specific interval. It respects platform user settings by skipping reminders for platform-managed users unless their specific OAuth client has emails enabled, and it records each sent reminder in the database to prevent duplicate notifications.
apps/web/app/api/cron/bookingReminder · high confidence
New cron job to automatically manage user time zones based on travel schedules
A new API route at /api/cron/changeTimeZone has been added to automatically update user and default schedule time zones in response to active or expired travel schedules. This cron job authenticates via an API key, identifies travel schedules that have started or ended within a specific window, and updates the user's time zone to the travel destination or reverts it to the original time zone, while also cleaning up expired travel schedule records.
apps/web/app/api/cron/changeTimeZone · high confidence
New cron job to sync selected calendars for delegation credentials
A new cron route at \/api/cron/selected-calendars\ has been added to automatically create and manage \SelectedCalendar\ records for users with Delegation Credentials. This job processes delegation user credentials, fetches their primary Google Calendar ID, and handles edge cases such as invalid grants or email mismatches (e.g., plus-addressing) by skipping problematic entries or reusing existing records. It works in conjunction with the existing credentials cron to ensure that calendar selections are correctly established for organization members using delegated access.
apps/web/app/api/cron/selected-calendars · high confidence
New cron route for scheduled webhook triggers
A new API route at /api/cron/webhookTriggers has been added to handle scheduled webhook processing. This endpoint authenticates requests using a CRON\_API\_KEY (via Authorization header or apiKey query parameter) and invokes the existing handleWebhookScheduledTriggers logic, ensuring it is wrapped with the standard App Directory error responder.
apps/web/app/api/cron/webhookTriggers · high confidence
New dedicated controller endpoints for atoms (conferencing, event types, schedules, verification)
The API now exposes dedicated controller files for atoms under /v2/atoms, splitting functionality previously bundled in a single controller. Users can now interact with conferencing apps (list installed apps), event types (list with team, get public/private types, update, bulk-update default location, get app integrations, get payment info), schedules (get, create, update, duplicate, get by event slug), and email verification (send/check/verify codes, manage verified emails). These endpoints are version-neutral, require authentication, and are excluded from public documentation as they are intended for internal platform atoms use.
apps/api/v2/src/modules/atoms/controllers · high confidence
New dedicated error page for authentication failures
A new dedicated error page has been added at /auth/error to handle and display specific authentication failure scenarios. This page parses query parameters to identify the error type and provides tailored messages for user creation errors, attempts to link accounts with mismatched identity providers (Google, Cal, SAML), SAML identity provider authority issues, and unverified email OAuth errors. If the error type is not recognized, it falls back to a generic login error message with the specific error code. Users are presented with a clear error icon and a button to return to the login page.
apps/web/app/(use-page-wrapper)/auth/error · high confidence
New deployment scripts for Codespaces and local setup
Added a new \deploy/\ directory containing \install.sh\ and \codespaces/install.sh\ to streamline the local development and Codespaces setup process. The main \install.sh\ script automates environment configuration by copying \.env.example\ to \.env\, generating secure \NEXTAUTH\_SECRET\ and \CALENDSO\_ENCRYPTION\_KEY\ values, installing dependencies via \yarn\, and invoking the Codespaces-specific installer. The Codespaces script provides a welcome message and hints to users to run \yarn dx\ for a quick dev environment. A \deploy/README.md\ was also added to direct users to the official documentation for full installation instructions.
deploy · high confidence
New developer and operational utility scripts added
A collection of new scripts has been added to the \scripts/\ directory to support development, testing, and operations. These include SQL utilities for database management (\auto-grant.sql\, \connection-activity.sql\, \delete-empty-google-credentials.sql\, \find-email-case-insensitive-duplicates.sql\, \get-table-storage-sizes.sql\), seeding tools for local environments and performance testing (\seed.ts\, \seed-app-store.ts\, \seed-booking-audit.ts\, \seed-huge-event-types.ts\, \seed-performance-testing.ts\, \seed-utils.ts\), and deployment/CI helpers (\staging-deploy.sh\, \vercel.sh\, \wait-for-it.sh\, \start.sh\, \replace-placeholder.sh\). Additionally, specific tooling was added for testing delegation credentials (\prepare-local-for-delegation-credentials-testing.js\), pulling UI components (\pull-coss-ui-components.ts\), reassigning attributes (\reassign-attributes.ts\), and testing Google Calendar webhooks (\test-gcal-webhooks.sh\).
scripts · high confidence
New development email preview endpoint and app credential sync webhook
A new GET endpoint at /api/email has been added to allow developers to preview rendered email templates (specifically MonthlyDigestEmail) in development mode, returning the HTML directly. Additionally, a new POST endpoint at /api/webhook/app-credential has been introduced to handle secure credential synchronization between apps and the Cal.com platform, validating requests via a shared secret and updating or creating user credentials in the database.
apps/web/app/api/email · high confidence
New email service for organization signup notifications
A new EmailModule and EmailService have been introduced in the v2 API to handle organization-related email communications. The service specifically implements a sendSignupToOrganizationEmail method that leverages existing platform libraries to dispatch signup notifications for organizations, including localization support via the provided locale.
apps/api/v2/src/modules/email · high confidence
New embed lifecycle documentation and core library structure
This change introduces the foundational structure for the Cal.diy embed system within the \packages/embeds\ directory. It adds comprehensive documentation (\LIFECYCLE.md\, \README.md\) detailing the handshake protocol, message formats, and lifecycle events (such as \\_\_iframeReady\, \linkReady\, and \bookerViewed\) for inline, modal, and floating button embeds. The diff also establishes the \embed-core\ package, including its entry points, initialization logic for iframe communication, and a Playwright-based test suite to verify embed behavior, namespaces, and theme handling.
packages/embeds · high confidence
New event type configuration UI components
This change introduces a suite of new React components for the event type settings interface, including a URL-controlled dialog wrapper, a bulk-edit modal for updating default locations across multiple event types, and specialized selectors for managing team members and child event types. It also adds UI tabs for configuring booking limits (including a new controller for the 'max active bookings per booker' setting) and recurring event rules, alongside helper components for form validation and documentation links.
packages/features/eventtypes · high confidence
New filter components for team selection and result display
The filters module now includes new UI components to enhance the filtering experience. The \TeamsFilter\ component allows users to search and select specific teams or filter by their own profile via a popover interface with checkboxes. Additionally, the \FilterResults\ component provides a standardized way to render query results, handling loading states with skeletons and displaying appropriate empty or no-results screens based on the data state.
apps/web/modules/filters · high confidence
New form field components for checkboxes and location selection
The form feature area now includes three new UI components: CheckboxField, which renders accessible checkboxes with optional descriptions and info badges; LocationSelect, a custom react-select wrapper for choosing meeting locations that displays specific icons (phone, video, map, etc.) and supports custom class names; and Select, a themed wrapper around react-select that handles dark/light mode styling and includes a SelectWithValidation variant for required fields. These components replace or supplement previous form implementations in this package.
packages/features/form · high confidence
New form input components: CheckedSelect, DatePicker, and MinutesField
The form UI library now includes three new components to enhance input capabilities. CheckedSelect provides a multi-select interface that displays selected options with avatars and labels, allowing users to easily remove items. DatePicker wraps the react-date-picker library to offer a styled date selection input with customizable minimum dates and disabled states. MinutesField renders a numeric input specifically designed for duration entries, featuring a 'mins' suffix and responsive layout for labels.
apps/web/components/ui/form · high confidence
New input validation schemas for OAuth client endpoints
Added input validation classes for the OAuth client module to enforce data types for authorization, code exchange, and token refresh operations. Specifically, \OAuthAuthorizeInput\ validates the redirect URI, \ExchangeAuthorizationCodeInput\ validates the client secret, and \RefreshTokenInput\ validates the refresh token with a descriptive API property for documentation purposes.
apps/api/v2/src/modules/oauth-clients/inputs · high confidence
New interactive components for the Getting Started onboarding flow
The Getting Started app now includes dedicated UI components to guide users through connecting apps and calendars. AppConnectionItem allows users to install integrations and set a default conferencing app, with clear feedback and dependency handling (e.g., prompting to connect a required account). ConnectedCalendarItem displays connected calendar accounts and lets users toggle individual calendars via UserCalendarSwitch. CreateEventsOnCalendarSelect provides a selector to choose which calendar new events are created on, and StepConnectionLoader offers skeleton placeholders while data loads.
apps/web/components/getting-started/components · high confidence
New main navigation layout and shell components for App Router
This change introduces the core layout and shell components for the main navigation area in the App Router. It adds \layout.tsx\ to handle session initialization and Sentry user identification, \ShellMainAppDir.tsx\ to render the page heading, subtitle, and call-to-action buttons with responsive styling, and \ShellMainAppDirBackButton.tsx\ as a client component providing a 'Go Back' button that navigates using Next.js router methods.
apps/web/app/(use-page-wrapper)/(main-nav) · high confidence
New modular shell architecture with KBar search and dynamic modals
The web application shell has been restructured into a modular layout within \apps/web/modules/shell\, introducing a centralized \Shell.tsx\ component that orchestrates the sidebar, top navigation, and content area. This update adds a global command palette (KBar) for quick navigation to event types, bookings, and settings, and introduces a \DynamicModals\ system to manage query-param-driven overlays like the new \WelcomeToCalcomModal\. The sidebar now features a profile switcher for organizations, while the mobile experience is enhanced with a bottom navigation bar and a dedicated 'More' menu for additional actions.
apps/web/modules/shell · high confidence
New multi-step app installation flow with account and event-type selection
The app installation process now uses a structured, multi-step UI. Users first select which account (personal or team) to install the app on via AccountsStepCard, then choose specific event types in EventTypesStepCard (which now renders descriptions as HTML and supports duration badges), and finally configure settings in ConfigureStepCard. The configuration step distinguishes between general apps and conferencing apps, using EventTypeAppSettingsWrapper for standard metadata and EventTypeConferencingAppSettings to handle location selection for conferencing integrations.
apps/web/components/apps/installation · high confidence
New onboarding wizard with structured setup steps
The getting-started flow has been restructured into a multi-step wizard to guide new users through profile and configuration setup. The new steps include UserSettings (collecting name and timezone), ConnectCalendars (linking a calendar and selecting a destination), ConnectedVideoStep (choosing a default conferencing app), SetupAvailability (configuring the default schedule), and UserProfile (setting the avatar and bio). This replaces the previous single-page or less-structured onboarding experience with a guided, sequential process.
apps/web/components/getting-started/steps-views · high confidence
New organizations repository for v2 managed teams
A new \OrganizationsRepository\ has been introduced in the v2 API to handle data access for managed organizations. This component provides methods to retrieve team and organization details by ID, slug, or associated user/client, and includes specific logic to identify platform organizations and verify admin API status. It also supports updating and deleting organization records, serving as the data layer for the new v2 managed organization feature.
apps/api/v2/src/modules/organizations/index · high confidence
New payment confirmation page for supported gateways
A new PaymentPage component and its corresponding App Router route have been added to display booking payment status. This page shows a summary of the event (title, time, location, price) and renders specific payment components for PayPal, Alby, HitPay, and BTCPay Server when a transaction is pending. The Stripe payment component has been removed from this view, and the page handles states for successful payments, refunds, and holds.
apps/web/app/(use-page-wrapper)/payment · high confidence
New permission decorator and Next-Auth guard for API v2
The API v2 module now includes a new \Permissions\ decorator and a \NextAuthGuard\. The decorator, located in \apps/api/v2/src/modules/auth/decorators/permissions\, creates a NestJS reflector decorator typed against \PERMISSIONS\ from \@calcom/platform-constants\, enabling fine-grained access control checks on endpoints. The guard, located in \apps/api/v2/src/modules/auth/guards/next-auth\, extends NestJS's \AuthGuard\ to use the 'next-auth' strategy, providing the authentication mechanism required for the decorator to function.
apps/api/v2/src/modules/auth/decorators/permissions, apps/api/v2/src/modules/auth/guards/next-auth · high confidence
New repository for team event type data access
A new \TeamsEventTypesRepository\ has been introduced to handle database operations for team event types. This component provides methods to retrieve event types by ID or slug, including associated data such as schedules, hosts, destination calendars, and Cal.com video settings. It also supports fetching event type children and managing user-specific team event types and host assignments, serving as the data access layer for the team event types module.
apps/api/v2/src/modules/teams/event-types · high confidence
New schedule management components and logic for date overrides and availability
This change introduces a new set of components and utilities for managing schedules, specifically focusing on date overrides and availability. The \DateOverrideInputDialog\ and \DateOverrideList\ components allow users to add, edit, and delete specific date overrides for their availability. The \ScheduleComponent\ and \ScheduleListItem\ provide the core UI for managing weekly schedules and listing existing schedules. Additionally, the \useTimesForSchedule\ hook and \date-ranges\ library handle the complex logic for calculating available time slots, including support for travel schedules and timezone adjustments. Comprehensive tests are included for time parsing, timezone handling, and date range calculations.
packages/features/schedules · high confidence
New self-hosted onboarding flow for admin user creation
The setup wizard now includes a dedicated step for creating the initial admin user, allowing self-hosted instances to configure credentials during installation. This change introduces the AdminUser component, which handles username, full name, email, and password input with strict validation (including password complexity and email format), and submits the data to the setup API before signing the user in. It also adds a StepDone component to display a completion state and navigate to the next wizard step.
apps/web/components/setup · high confidence
New server-side props handler for public user booking pages
This change introduces a new \getServerSideProps\ implementation for the \/\[user\]\ route, centralizing the server-side data fetching for public user profiles. It handles organization context redirections, resolves dynamic user groups, and fetches user profile details (including branding and SEO settings) along with their public event types. The logic ensures that users with a single public event type are redirected to that event, while also preparing the necessary props for rendering the booking page with correct organization branding and user metadata.
apps/web/server/lib/\[user\] · high confidence
New settings components for secondary email and two-factor authentication
The settings area now includes dedicated UI components to manage secondary email addresses and two-factor authentication (2FA). Users can add, verify, and manage secondary emails via the new CustomEmailTextField, SecondaryEmailModal, and SecondaryEmailConfirmModal, which handle validation and status badges. Additionally, the EnableTwoFactorModal and DisableTwoFactorModal provide a guided, step-by-step interface for setting up and removing 2FA, including QR code scanning, backup code management, and auto-submission when TOTP codes are fully entered. These components rely on the new TwoFactorAuthAPI for backend communication.
apps/web/components/settings · high confidence
New setup UIs for calendar and email integrations
Added dedicated setup components for Apple Calendar, CalDAV, Exchange 2013, Exchange 2016, Exchange, and Sendgrid integrations. These new pages provide a consistent interface for users to input credentials (such as Apple ID, CalDAV URLs, Exchange server details, and Sendgrid API keys) and validate them before saving. The Exchange integration specifically supports selecting authentication methods (Standard or NTLM) and specific Exchange versions, while the Sendgrid integration includes a live API key test feature to verify connectivity before finalizing the setup.
(repo-wide) · high confidence
New theme configuration and color generation utilities
The theme configuration package now includes a new \generateColor\ utility that automatically creates a 10-shade color palette (50–900) from a single hex input, alongside TypeScript interfaces for color and shade definitions. Additionally, a new \shared-sources.css\ file has been added to explicitly register source paths for Tailwind CSS scanning across the web app, modules, components, and UI packages, ensuring consistent style generation. The \tokens.css\ file has been updated to define extensive design tokens for colors, radii, shadows, and animations, including specific 'Cal.diy' variants and semantic color mappings.
packages/config · high confidence
New token management module for API v2
A new tokens module has been introduced in API v2 to handle OAuth 2.0 token lifecycle and validation. The implementation includes a repository for creating, invalidating, and refreshing access and refresh tokens (with access tokens expiring in 60 minutes and refresh tokens in one year) via Prisma, and a service that validates access tokens by checking the database or decoding third-party JWTs using the CALENDSO\_ENCRYPTION\_KEY.
apps/api/v2/src/modules/tokens · high confidence
New two-factor authentication setup and management UI
The security settings page now includes a dedicated Two-Factor Authentication section that allows users to enable, disable, and manage 2FA directly in the web app. This change introduces a new \TwoFactorAuthSection\ component along with supporting modals (\EnableTwoFactorModal\, \DisableTwoFactorModal\) and an API client (\TwoFactorAuthAPI\) to handle the TOTP setup flow (password confirmation, QR code display, code entry) and disabling. The enable flow features an auto-submit capability that triggers immediately once the six-digit code is fully entered, streamlining the activation process for users.
apps/web/components/security · high confidence
New unified calendar module with Google integration and caching
A new NestJS module has been introduced to manage unified calendars, providing a centralized structure for calendar-related operations. This module wires together services for Google Calendar integration, unified calendar management, and free/busy lookups, while leveraging Redis for caching and existing repositories for credentials, bookings, and user data. It exposes its functionality via a dedicated controller and exports the Google Calendar service for use by other parts of the application.
apps/api/v2/src/modules/cal-unified-calendars · high confidence
New unified calendar service layer for Google Calendar operations
This change introduces a new \UnifiedCalendarService\ and supporting services (\GoogleCalendarService\, \UnifiedCalendarsFreebusyService\) in the API v2 codebase to provide a connection-based interface for Google Calendar interactions. The new service layer enables retrieving event details, updating events via PATCH, listing events, creating and deleting events, and querying free/busy times. It handles authentication by attempting delegation (service account impersonation) first, falling back to direct OAuth if needed, and supports both user-scoped and connection-scoped calendar operations. The implementation is accompanied by comprehensive unit and integration tests for the new services.
apps/api/v2/src/modules/cal-unified-calendars/services · high confidence
New upgrade page added to the web application
A new \UpgradePage\ component has been introduced at \apps/web/modules/upgrade/upgrade-view.tsx\. This page serves as the user interface for the organization upgrade flow, utilizing the \Shell\ layout and displaying either an upgrade prompt or a confirmation message via \EmptyScreen\ components. It integrates with the tRPC client to fetch upgrade data and provides actions to trigger the upgrade mutation or contact support.
apps/web/modules/upgrade · high confidence
New user management architecture with DI, repositories, and services
The \packages/features/users\ directory now provides a structured foundation for user management, introducing a dependency-injection setup (Membership and Profile modules), a comprehensive \UserRepository\ for data access, and a \UserCreationService\ that enforces watchlist checks during signup. This location also includes routing logic for team hosts and integration tests for the new repository layer.
packages/features/users · high confidence
New user management components and tests in the users module
This change introduces a suite of new React components and tests within the \apps/web/modules/users\ directory to support enhanced user administration and profile management. Key additions include \AdminPasswordBanner\ to alert inactive admins about 2FA or password requirements, and several banner components (\CalendarCredentialBanner\, \InvalidAppCredentialsBanner\) to surface credential issues. The update also brings a comprehensive \UserTable\ implementation featuring bulk actions (delete, dynamic link generation, event type assignment), an \EditUserSheet\ with inline editing capabilities, and a \PlatformManagedUsersTable\ for platform-level user oversight. A test file for \AdminPasswordBanner\ is also added to verify its rendering logic.
apps/web/modules/users · high confidence
New v2 API endpoints for verifying and managing user and team email and phone resources
This change introduces the \verified-resources\ module in the v2 API, providing endpoints to request verification codes for and verify email addresses and phone numbers for both individual users and teams. The new \/v2/verified-resources\ controller exposes routes to request verification codes (with rate limiting), verify codes, and retrieve lists or specific details of verified emails and phone numbers. The implementation includes input/output DTOs for Swagger documentation, a service layer integrating with platform libraries for sending codes and validating tokens, and repository classes for querying the database via Prisma.
apps/api/v2/src/modules/verified-resources · high confidence
New v2 API services for Zoom, Office 365 Video, and Google Meet integration
The conferencing module now includes dedicated services for managing Zoom, Office 365 Video, and Google Meet connections. These services handle OAuth flows for Zoom and Office 365, validate Google Calendar prerequisites for Google Meet, and manage credential storage for both users and teams. This enables users to connect and set default conferencing apps directly through the v2 API.
apps/api/v2/src/modules/conferencing/services · high confidence
New v2 API services for team event type management
The API v2 now includes dedicated services for managing team event types, introducing \TeamsEventTypesService\ and \OutputTeamEventTypesService\. These services enable the creation, retrieval, updating, and deletion of event types specifically scoped to teams, handling team-specific attributes such as hosts, scheduling types (including managed, collective, and round-robin), and team metadata. The output service ensures that team event type responses correctly map internal scheduling types and include associated team details like name, slug, and branding.
apps/api/v2/src/modules/teams/event-types/services · high confidence
New v2 Slots API endpoint for 2024-09-04 version
The API now exposes a new controller for the 2024-09-04 version of the Slots API, allowing users to retrieve available time slots for event types. This endpoint supports multiple query methods, including searching by event type ID, event type slug combined with username or team slug, and dynamic event availability by usernames. It also supports organization-scoped searches via organizationSlug and includes parameters for time range (start/end), time zone, duration, and slot format. The endpoint requires the cal-api-version header to be set to 2024-09-04.
apps/api/v2/src/modules/slots/slots-2024-09-04/controllers · high confidence
New v2 conferencing API controller and e2e tests
This change introduces the new v2 API controller for conferencing applications, located at \/v2/conferencing\. It exposes endpoints to list installed conferencing apps, connect non-OAuth apps (like Google Meet), generate OAuth URLs for apps like Zoom and Office 365 Video, and handle OAuth callbacks. The controller also supports setting a default conferencing app and disconnecting apps. An accompanying end-to-end test suite validates these flows, including dependency checks (e.g., requiring Google Calendar connection before Google Meet) and state management for team/organization-level installations.
apps/api/v2/src/modules/conferencing/controllers · high confidence
New v2 slots service implementation with input/output transformation and reservation logic
The v2 slots API (version 2024-09-04) now uses a dedicated service layer that separates query transformation, slot formatting, and business logic. The new \SlotsInputService\ handles incoming requests by resolving event types via ID, username, or team slug, and normalizes time ranges. The \SlotsOutputService\ formats available slots into time-based or range-based views, supporting timezone adjustments and seated event details (seats booked/remaining). The core \SlotsService\ orchestrates availability checks and slot reservations, including validation for overlapping bookings, round-robin host availability, and custom reservation durations for authenticated users. A new \SlotsRepository\ manages slot creation, updates, and overlap detection in the database.
apps/api/v2/src/modules/slots/slots-2024-09-04/services · high confidence
New v2 unified calendar API for managing Google Calendar connections and events
The v2 API now exposes a new \/v2/calendars\ endpoint group that allows users to manage their connected calendar accounts and perform CRUD operations on events. The \GET /connections\ endpoint lists all linked calendar providers (Google, Office 365, Apple) while safely stripping sensitive credential keys from the response. For Google Calendar connections specifically, users can now list, create, retrieve, update, and delete events via scoped endpoints like \GET /connections/:connectionId/events\ and \PATCH /connections/:connectionId/events/:eventId\. These endpoints support filtering by date range and specific calendar IDs, with the controller handling timezone normalization and input validation.
apps/api/v2/src/modules/cal-unified-calendars/controllers · high confidence
New webhook access guards for platform OAuth clients and user event types
Added three new API v2 webhook guards to enforce stricter access control: IsOAuthClientWebhookGuard validates that a webhook belongs to the requesting OAuth client (with system admin fallback if the organization ID mismatches), IsUserEventTypeWebhookGuard ensures users can only access webhooks tied to their own event types, and IsUserWebhookGuard restricts webhook access to the webhook owner or system admins. These guards protect webhook endpoints by verifying ownership and association before allowing requests to proceed.
apps/api/v2/src/modules/webhooks/guards · high confidence
New webhook services for event types, teams, users, and OAuth clients
This change introduces dedicated service classes in the API v2 webhooks module to manage webhook subscriptions for specific scopes: event types, teams, users, and platform OAuth clients. Each service enforces URL validation via \validateWebhookUrl\ before creation, prevents duplicate subscriber URLs by throwing a \ConflictException\, and restricts the \DELEGATION\_CREDENTIAL\_ERROR\ trigger to organization-level webhooks only. The services also provide paginated retrieval and bulk deletion capabilities, while the general \WebhooksService\ handles updates with conditional URL validation and deletion for existing webhooks.
apps/api/v2/src/modules/webhooks/services · high confidence
New weekly calendar view with time-blocking and availability management
A new weekly scheduler view has been added to the web application, featuring a grid-based layout for visualizing and managing time slots. This view includes a current-time indicator that updates on page refocus, support for blocking out unavailable times, and the ability to display available slots and 'out of office' statuses. Users can interact with the calendar by clicking empty cells to create bookings, and the view handles event overlaps and selection states. Additionally, the calendar settings wrapper now provides a unified interface for managing connected calendar integrations and toggling specific calendars for both user-level and event-type-level scheduling.
apps/web/modules/calendars · high confidence
OAuth client user management and token flow implementation
The API v2 now supports creating, retrieving, and updating managed users scoped to specific OAuth clients, including automatic email suffixing to prevent collisions and default schedule/calendar setup. Additionally, the OAuth flow service introduces Redis-backed caching for access token validation and propagation, ensuring faster token checks while maintaining fallback to the database, and exposes endpoints to exchange authorization tokens and refresh access tokens with explicit expiry times.
apps/api/v2/src/modules/oauth-clients/services · high confidence
PayPal integration now includes a dedicated setup page and payment component
Users can now configure their PayPal Business account credentials directly within the app via a new Setup page (Setup.tsx), which guides them through creating a PayPal Developer app and saving the Client ID and Secret Key. Additionally, a new payment interface (PaypalPaymentComponent.tsx) has been introduced to handle the actual transaction flow, parsing payment data to generate an 'Pay with PayPal' button that directs users to the appropriate PayPal approval URL.
apps/web/components/apps/paypal · high confidence
Placeholder PBAC support added to API v2
The API v2 now includes a Permission-Based Access Control (PBAC) decorator and guard. Since PBAC is not available in the community edition, the guard is implemented as a pass-through that always allows access, ensuring the API layer remains compatible with PBAC-protected endpoints without enforcing actual permission checks.
apps/api/v2/src/modules/auth/decorators/pbac, apps/api/v2/src/modules/auth/guards/pbac · high confidence
Repository rebranded to Cal.diy with official Docker support and updated configuration templates
The project has been rebranded from 'Calendso' to 'Cal.diy', reflected across all configuration files, documentation, and environment templates (e.g., \.env.example\, \.env.appStore.example\). This change includes the introduction of an official \Dockerfile\ and \.dockerignore\ to support containerized deployments, alongside updated deployment templates for Heroku (\app.json\) and Gitpod (\.gitpod.yml\). The repository also adopts Yarn 4.12.0 via \.yarnrc.yml\ and introduces new developer guidelines in \AGENTS.md\ and \SPEC-WORKFLOW.md\ to standardize contribution workflows.
(repo-wide) · high confidence
Send attendee no-show data to Salesforce
The system now automatically sends attendee no-show information to Salesforce. This is implemented by a new handler that checks event type metadata for CRM apps, specifically targeting Salesforce, and uses the CRM manager to transmit the no-show status of attendees associated with a booking.
packages/features/noShow · high confidence
Stripe Connect integration for API v2
This change introduces the Stripe module for the API v2, enabling users to connect their Stripe accounts via OAuth. The new \StripeController\ exposes endpoints to retrieve a Stripe Connect authorization URL, handle the OAuth callback to save credentials (with support for proxying to organization/team-level endpoints), and verify the connection status. The implementation includes the necessary service logic, data transfer objects, and utility schemas to manage the Stripe OAuth flow and credential storage.
apps/api/v2/src/modules/stripe · high confidence
Unified calendar API input validation and Google Calendar data transformation
This change introduces the input validation schemas and data transformation logic required for the new unified calendar API. It adds structured input classes for creating, listing, and updating calendar events, as well as checking free/busy time, ensuring proper validation of dates, time zones, and attendees. Additionally, it implements pipes to transform raw Google Calendar event data into a unified internal format for retrieval and to transform unified update requests into the specific payload format required by the Google Calendar API.
apps/api/v2/src/modules/cal-unified-calendars/pipes · high confidence
Webhook management for specific event types
Users can now create, update, retrieve, and delete webhooks associated with individual event types via the API v2 endpoints under \/v2/event-types/:eventTypeId/webhooks\. This change introduces a new controller and corresponding end-to-end tests that enforce ownership, ensuring users can only manage webhooks for event types they own.
apps/api/v2/src/modules/event-types/controllers · high confidence
Removals
Removed default Next.js template files
The default files generated by Create Next App have been removed from the pages directory. This includes the main application wrapper (\_app.js), the sample API route (pages/api/hello.js), and the default home page (pages/index.js), clearing the way for custom application code.
pages · high confidence
Security
App description parsing now uses js-yaml with JSON schema for security
The \getStaticProps\ module in the app slug handler has been updated to replace \gray-matter\ with \js-yaml\ (using \yaml.JSON\_SCHEMA\) for parsing YAML frontmatter in app \DESCRIPTION.md\ files. This change improves security by preventing unsafe YAML type injection (such as arbitrary JavaScript dates) and ensures compatibility with js-yaml 4.x. The implementation now explicitly validates that parsed frontmatter is an object and safely handles invalid YAML, while the new test suite verifies correct parsing of items, iframes, and edge cases like missing frontmatter or non-object roots.
apps/web/lib/apps/\[slug\] · high confidence
SSRF protection for team logo URLs
Team logo fields are now validated against Server-Side Request Forgery (SSRF) risks. The new \SSRFSafeUrlValidator\ ensures that only HTTPS URLs and image data URLs are accepted, while blocking HTTP, private IPs, metadata endpoints, and other unsafe schemes, preventing potential security vulnerabilities when the system fetches these resources.
apps/api/v2/src/modules/teams/teams/validators · high confidence
Webhook URL validation prevents SSRF attacks
Webhook endpoints now validate subscriber URLs before accepting them, blocking requests to private IP addresses, localhost, and other unsafe hosts to prevent Server-Side Request Forgery (SSRF). This validation is enforced via a new utility that checks URLs against security rules, ensuring only safe, public endpoints can be configured for webhooks.
apps/api/v2/src/modules/webhooks/utils · high confidence
API
Added Swagger DTOs for unified calendar event locations and connection listing
This change introduces new API response schemas for the unified calendars module, enabling proper Swagger documentation for client integrations. It defines detailed output structures for calendar event locations, supporting video, phone, SIP, and additional link types with their specific access details (URLs, passwords, PINs, meeting codes). It also adds a dedicated output schema for listing connected calendar accounts, exposing the connection ID, provider type, and primary email for each linked calendar.
apps/api/v2/src/modules/cal-unified-calendars/outputs · high confidence
Define managed user API response schemas
The API now explicitly defines the response structures for managed user operations (create, read, update, delete). The \ManagedUserOutput\ schema exposes user profile fields including id, email, username, name, bio, timeZone, weekStart, createdDate, timeFormat, defaultScheduleId, locale, avatarUrl, and metadata. These schemas are used by the create, get, update, and delete managed user endpoints to standardize the returned data format and improve API documentation via Swagger decorators.
apps/api/v2/src/modules/oauth-clients/controllers/oauth-client-users/outputs · high confidence
Architecture
Apps store components migrated to web modules
The app store UI components (including AppCard, AllApps, AdminAppsList, and various sliders) have been moved from the shared features package into the apps/web/modules directory. This change consolidates tRPC-dependent and web-specific rendering logic within the web application, separating it from the broader features library.
apps/web/modules/apps/components · high confidence
Centralize tRPC client and context setup in the App Router
The tRPC infrastructure for the web app is now consolidated into the \apps/web/app/\_trpc\ directory, providing a single source of truth for client-side and server-side integration. This includes a new \TrpcProvider\ component that wraps the application with both the tRPC and React Query providers, a dedicated \queryClient\ configuration that prevents unnecessary retries on authorization or validation errors, and a \trpcClient\ that handles endpoint resolution and batching. On the server side, a new \createRouterCaller\ utility and \getTRPCContext\ function streamline how routers are invoked within the App Router, ensuring consistent context building via legacy request adapters.
_apps/web/app/\trpc · high confidence
Event types module restructured into new component architecture
The event types feature has been refactored to use a new modular component structure within apps/web/modules/event-types. This change introduces dedicated components for core interactions, including AddVerifiedEmail for managing verified sender addresses, CheckedUserSelect for assigning team members, and CreateEventTypeDialog/DuplicateDialog for managing event type lifecycles. The layout and display logic is now handled by EventType, EventTypeLayout, and EventTypeDescription, while state management and routing are centralized in EventTypeWebWrapper. Supporting UI elements like MultiDropdownSelect, MultiplePrivateLinksController, and various skeleton loaders have also been added to support the new module-based organization.
apps/web/modules/event-types · high confidence
Introduce dependency injection for booking and availability services
The \packages/features/di\ location now provides a dependency injection composition root for core booking and availability logic. This change adds DI containers and modules for services such as AvailableSlots, BusyTimes, CheckBookingLimits, GetUserAvailability, and ManagedEventReassignment, wiring them to repositories like Booking, EventType, and User via the \@evyweb/ioctopus\ library. It also includes integration tests for the FeatureRepository to validate the new caching and DI behavior.
packages/features/di · high confidence
Migrate deployment and selected slots data access to feature-scoped repositories
The data access logic for deployment details and selected time slots has been moved from the shared library into their respective feature packages. This introduces specific repository implementations (\DeploymentRepository\ and \PrismaSelectedSlotRepository\) along with their interfaces and DTOs, centralizing how license keys, signature tokens, and slot reservation data are retrieved and managed within the application's architecture.
packages/features/deployment, packages/features/selectedSlots · high confidence
Migrate signup page to App Router with server-side props
The signup page logic has been moved from the pages directory to the App Router structure, implemented via a new \getServerSideProps.tsx\ file in \apps/web/lib/signup\. This change centralizes the server-side data fetching for the signup flow, including validation of query parameters (username, email, redirect URL) and verification tokens, while integrating with the \FeaturesRepository\ to check feature flags like email verification and onboarding V3. It also handles redirection for authenticated users and manages team/organization context for invite-based signups.
apps/web/lib/signup · high confidence
New membership repository and service layer
The membership feature now uses a dedicated repository and service architecture. A new MembershipRepository handles database queries for team memberships, including checks for accepted members and lookups by user ID. A PrismaOrgMembershipRepository specifically manages organization-level admin checks. A MembershipService provides a high-level API to check if a user is a member, admin, or owner of a team, returning a structured result with role details.
packages/features/membership · high confidence
Refactored App List and Management Components
Moved the App List, App Set Default Link Dialog, and Disconnect Integration Modal components from the web application into the shared features package. This change decouples the app store UI from the web router and atoms, improving code organization and reusability across different parts of the application.
packages/features/apps/components · high confidence
Refactored feature flags to use dependency-injected, cached repositories with tri-state inheritance
The feature flag system in \packages/features/flags\ has been restructured to replace the monolithic \FeaturesRepository\ with a split architecture of Prisma and Cached layers for global, user, and team features, wired together via a dependency injection container. This change introduces tri-state semantics (enabled, disabled, inherit) for user and team feature assignments, allowing explicit overrides that block inheritance from parent teams or organizations. Cached repositories now wrap the Prisma implementations using \@Memoize\ and \@Unmemoize\ decorators to improve performance, while a new React \FeatureProvider\ and \useFlagMap\ hook make flag values available throughout the application context.
packages/features/flags · high confidence
Relocated data-table components and hooks to a dedicated web module
The data-table implementation has been moved from the shared \features\ directory into a new \apps/web/modules/data-table\ location. This change consolidates the table's core provider, context, and UI components—including the main \DataTable\ component, \DataTableWrapper\, \DataTableToolbar\, \DataTablePagination\, \DataTableSelectionBar\, and the full suite of filter components (such as \ActiveFilters\, \AddFilterButton\, \DateRangeFilter\, and \ColumnVisibilityButton\)—into a single, web-specific module. This restructuring centralizes the table's state management and rendering logic within the web application layer.
apps/web/modules/data-table · high confidence
Webhook system refactored with versioned payload builders and async tasker architecture
The webhook delivery system in \packages/features/webhooks\ has been restructured to support versioned payloads and asynchronous processing. A new \WebhookService\ and \WebhookTaskConsumer\/\WebhookTaskerProducerService\ architecture separates lightweight task queuing from heavy payload building and HTTP delivery. Payload construction is now handled by version-specific builders (e.g., \BookingPayloadBuilder\ for v2021-10-20) that implement abstract base classes, allowing for future versioning and consistent payload structures across events like \BOOKING\_CREATED\, \MEETING\_STARTED\, and \OOO\_CREATED\. This change introduces a more robust, testable, and scalable foundation for webhook integrations.
packages/features/webhooks · high confidence
Behavioural changes
1 commit (0 fixes) modifying .yarn/releases
A change to existing behaviour in .yarn/releases — 1 commit, 1 file: “chore: upgrade yarn from 3.4.1 to 4.12.0 (\#26102)” (refs \#26102).
.yarn/releases · low confidence · unverified
API v2 introduces structured input and output DTOs for user management
The API v2 now defines explicit input and output classes for user operations, replacing ad-hoc request handling with validated data structures. For creating and updating users, the system now enforces specific formats for time zones (capitalized), time formats (12/24), and locales, while also supporting optional fields like bio, avatar URL, and metadata with strict key/value limits. The update-managed-user input specifically allows modifying the default schedule ID, whereas the create-managed-user input does not. Additionally, the GET users endpoint now supports filtering by email address (single or array) and pagination (take/skip), with output DTOs exposing all user profile fields including theme, branding, and schedule details.
apps/api/v2/src/modules/users/inputs · high confidence
Add loading state and security checks to webhook edit page
The webhook edit page now includes a dedicated loading component that displays a skeleton UI while data is being fetched, improving perceived performance. Additionally, the page enforces strict ownership checks: it verifies that the current user has an active session and possesses the necessary permissions (Admin, Owner, or Member) to access the specific webhook, redirecting unauthorized users to the login page or returning a 404 if access is denied.
apps/web/app/(use-page-wrapper)/settings/(settings-layout)/developer/webhooks/\[id\] · high confidence
Add loading state and server-side data fetching for Calendars settings page
The Calendars settings page now includes a dedicated loading component that displays a skeleton loader while data is being fetched. The page itself has been converted to a server component that concurrently fetches connected calendars and installed calendar integrations via TRPC, passing this data to the CalendarListContainer for rendering.
apps/web/app/(use-page-wrapper)/settings/(settings-layout)/my-account/calendars · high confidence
Added output DTOs for conferencing app management endpoints
New response data transfer objects have been introduced for the v2 conferencing API to standardize how client-facing data is structured and documented. These include \GetConferencingAppsOauthUrlResponseDto\ for OAuth URL retrieval, \ConferencingAppsOutputResponseDto\ and \ConferencingAppOutputResponseDto\ for listing and retrieving individual app credentials (including the optional \invalid\ status field), \GetDefaultConferencingAppOutputResponseDto\ for fetching the default app slug and link, and \SetDefaultConferencingAppOutputResponseDto\ for setting the default. All DTOs use NestJS Swagger decorators to provide API documentation and validation rules for the response payloads.
apps/api/v2/src/modules/conferencing/outputs · high confidence
Added server-side caching and revalidation for membership, travel schedules, and settings paths
New cache modules have been introduced in the web application to optimize data fetching for specific user contexts. The membership cache provides a server-side cached check for team plan status with associated revalidation logic. A travel schedule cache wraps the repository to fetch user-specific travel data with tag-based revalidation. Additionally, specific revalidation functions are now available for the My Account settings paths (profile and calendars), enabling targeted cache invalidation when those sections are updated.
apps/web/app/cache · high confidence
Admin feature flags page now uses modular FlagListingView
The admin feature flags settings page has been updated to import and render the FlagListingView component from the new @calcom/web/modules/feature-flags/views location, replacing the previous implementation. This change reflects the broader refactoring that moved feature-flags components from the packages/features directory into the apps/web/modules structure, ensuring the admin UI correctly consumes the relocated module while maintaining the same SettingsHeader layout and metadata generation.
apps/web/app/(use-page-wrapper)/settings/(admin-layout)/admin/flags · high confidence
Admin playground page now uses consistent layout
The admin playground page now uses the same layout as other pages in the settings area, providing a consistent user experience. The page includes a header with title and description, and displays a list of available playground components (currently just the Date Range Filter) with icons and descriptions.
apps/web/app/(use-page-wrapper)/settings/(admin-layout)/admin/playground · high confidence
Admin settings layout now enforces server-side permission checks
The admin settings layout has been refactored to move the user role verification from the client to the server. The new server component fetches the session and redirects non-admin users to the profile page before rendering the layout, preventing any flash of unauthorized content. The client component now solely handles the UI structure and error boundaries for the admin settings pages.
apps/web/app/(use-page-wrapper)/settings/(admin-layout) · high confidence
Admin user edit page now uses Next.js App Router with error handling
The admin user edit page has been migrated to the Next.js App Router, introducing a dedicated error.tsx file that displays a user-friendly alert when an error occurs. The page.tsx component now leverages the UserRepository for data fetching and includes input validation via Zod, ensuring that invalid user IDs result in a clear error message rather than a silent failure. This change improves the robustness and user experience of the admin user editing workflow.
apps/web/app/(use-page-wrapper)/settings/(admin-layout)/admin/users/\[id\] · high confidence
Admin users settings pages now use the new SettingsHeader layout
The Admin Users listing and Add User pages have been updated to use the new SettingsHeader component for their layout. This change standardizes the visual presentation of these pages within the admin settings, ensuring consistent headers and descriptions, and adds a direct link to add a new user from the main users listing page.
apps/web/app/(use-page-wrapper)/settings/(admin-layout)/admin/users · high confidence
Agent configuration and skills relocated to agents directory
The .cursor/rules and .cursor/skills files are now symbolic links pointing to ../agents/rules and ../agents/skills respectively. This change consolidates agent-related configuration and skills into a dedicated agents directory, simplifying the project structure while maintaining the same functionality for the Cursor agent.
.cursor · high confidence
App Store CLI introduces non-interactive app creation and Windows compatibility fixes
The App Store CLI now supports a non-interactive mode for the \create\ command, allowing developers to bypass prompts by providing \--name\, \--description\, \--category\, and \--template\ flags directly. This change also includes several Windows compatibility fixes, such as handling path separators correctly and ensuring the CLI functions properly on Windows environments. Additionally, the CLI now supports creating, editing, and deleting apps and templates via a unified interface, with templates like \link-as-an-app\ requiring an \--external-link-url\ flag.
packages/app-store-cli · high confidence
App installation flow restructured into a multi-step wizard
The app installation process in the web application has been refactored into a structured, multi-step wizard. This change introduces a new module at \apps/web/modules/apps/installation\ that manages the onboarding flow through distinct stages: selecting accounts, choosing event types, and configuring the app. The implementation leverages the \AppOnboardingSteps\ enum to define the sequence and uses the \sonner\ library for toast notifications, replacing the previous \toaster\ component. This provides a more guided and consistent user experience when installing new applications.
apps/web/modules/apps/installation · high confidence
App repository now validates keys on seed and logs errors via Sentry
The new PrismaAppRepository ensures that apps are only enabled during seeding if their required configuration keys are valid, and it adds Sentry error logging to the findAppStore query to improve observability when app retrieval fails.
packages/features/apps/repository · high confidence
Apps page migrated to React Server Components
The /apps page has been converted from a server-side rendered page using getServerSideProps to a React Server Component (RSC). This change moves the AppsView component to a client-side entry point that composes server-rendered data with interactive UI elements, improving performance and aligning with the application's App Router migration strategy.
apps/web/modules/apps · high confidence
Auth API endpoints now capture tracking data and handle email verification
The authentication API surface has been updated to support tracking attribution and email verification workflows. The main NextAuth handler (\[...nextauth\].ts) now extracts tracking identifiers (such as Dub IDs or click IDs) from cookies and query parameters, passing this context to the authentication options to ensure user creation events are attributed correctly. Additionally, a new verify-email endpoint has been introduced to manage email confirmation processes, delegating the actual verification logic to the shared library implementation.
apps/web/pages/api/auth · high confidence
Auth module restructured with new UI views and security enhancements
The authentication module has been reorganized into a dedicated \apps/web/modules/auth\ directory, introducing new React components for login, signup, password reset, and OAuth flows. This update includes a new Turnstile widget for Cloudflare bot protection, CSRF token handling for the forgot-password flow to prevent cross-site request forgery, and debounced email submission to reduce server load. The login experience now displays a 'Last Used' indicator for login methods, while the email verification page provides direct links to Gmail, Outlook, and Yahoo. Additionally, trusted OAuth clients can now auto-skip the consent screen, and the OAuth authorize view supports account selection for team profiles.
apps/web/modules/auth · high confidence
Auth verification page moved to stable route
The email and payment verification page has been moved from the /future directory to its permanent location at /auth/verify. This change stabilizes the route structure for users completing account verification or payment confirmation flows, ensuring consistent access to the verification interface without relying on experimental routing prefixes.
apps/web/app/(use-page-wrapper)/auth/verify · high confidence
Authentication guard added to installed apps routes
The installed apps pages now enforce authentication before rendering content. If a user is not logged in, they are redirected to the login page, ensuring that access to installed application data is restricted to authenticated users.
apps/web/app/(use-page-wrapper)/apps/installed · high confidence
Availability management views migrated to App Router modules
The availability management interface has been restructured to use the App Router, introducing new client-side view components for the schedule list, individual schedule editing, and troubleshooting. Users will now interact with the availability list and schedule settings through these new module components, which handle schedule creation, updates, deletion, and bulk default availability assignments via tRPC mutations, while maintaining existing functionality for managing schedules and event type defaults.
apps/web/modules/availability · high confidence
Availability page migrated to Next.js App Router with server-side caching
The /availability page has been rebuilt using the Next.js App Router, introducing server-side rendering and data fetching. The page now utilizes tRPC with unstable\_cache to fetch and cache availability data for one hour, reducing redundant client-side requests. To support this architecture, new files have been added: a server action for path revalidation, an error boundary for handling failures, a loading skeleton for improved perceived performance, and the main page component that orchestrates session checks, data retrieval, and UI rendering.
apps/web/app/(use-page-wrapper)/(main-nav)/availability · high confidence
Availability schedule page migrated to App Router with server-side data fetching
The availability schedule page has been rebuilt for the Next.js App Router, replacing the previous implementation with a server component that fetches schedule and travel schedule data via tRPC. This change introduces a dedicated server action for path revalidation, a loading state that displays a detailed skeleton UI matching the page layout, and simplified metadata generation. Users will experience server-side rendering for the schedule view, with improved loading states and the ability to revalidate the page cache after updates.
apps/web/app/(use-page-wrapper)/availability/\[schedule\] · high confidence
Avatar API now converts SVGs to PNG and uses App Router
The avatar API endpoint has been migrated to the Next.js App Router and now automatically converts SVG avatar images to PNG format before serving them. This ensures consistent image handling and compatibility across all clients, while also improving performance by caching the converted PNG versions in the database.
apps/web/app/api/avatar · high confidence
Billing webhooks disabled in community edition
The Stripe webhook API endpoint now returns a 404 error with the message "Billing webhooks are not available in community edition" for all requests. This change ensures that billing-related webhook processing is explicitly blocked in the community edition, preventing unintended billing operations.
apps/web/pages/api/stripe · high confidence
Booking confirmation pages are no longer indexed by search engines
The booking confirmation and dry-run success pages now explicitly set \robots: { index: false, follow: false }\ in their metadata. This prevents search engines from indexing these pages, which contain sensitive user data and duplicate content, ensuring they do not appear in search results.
apps/web/app/(booking-page-wrapper)/booking · high confidence
Booking reference repository moved to features domain with integration tests
The BookingReferenceRepository implementation and its interface have been moved from the shared lib directory into the bookingReference feature folder, establishing a dedicated location for booking reference data access logic. This change includes the addition of comprehensive integration tests for the repository to verify correct behavior when replacing booking references, ensuring that existing references are soft-deleted and new ones are created as expected.
packages/features/bookingReference · high confidence
CSRF token endpoint now supports configurable cookie attributes for embedded contexts
The new /api/csrf endpoint allows clients to specify the SameSite attribute for the CSRF cookie via a query parameter, defaulting to 'lax' but accepting 'strict' or 'none' (when using HTTPS). This enables the CSRF protection mechanism to function correctly in embedded iframe contexts where stricter cookie policies might otherwise block the token.
apps/web/app/api/csrf · high confidence
Cal Video server-side logic migrated to App Router and repositories
The server-side data fetching for Cal Video booking pages (including the main meeting view and the 'meeting not started' state) has been migrated from the legacy Pages Router to the Next.js App Router using new \getServerSideProps.ts\ files. This change replaces direct Prisma calls with dependency-injected repository classes (\BookingRepository\, \EventTypeRepository\, \UserRepository\) and introduces logic to handle Cal Video-specific settings, such as automatic transcription and recording permissions, as well as meeting token expiration updates.
apps/web/lib/video/\[uid\] · high confidence
Centralized SEO configuration with Twitter handle
A new centralized SEO configuration file has been added to define default metadata for the application. This change explicitly sets the Twitter handle and site to @calcom, addressing previous issues with hardcoded or missing Twitter metadata in SEO settings. Users will see consistent social media preview data across the site.
apps/web/lib/config · high confidence
Centralized event type access control logic
A new \EventTypeAccessService\ has been introduced to centralize the logic for determining whether a user has administrative or ownership permissions for a specific event type. This service evaluates access by checking if the user is a system admin, the event owner, a host or assignee of the event, a team/parent-org admin, or an org admin/owner of the event owner, providing a unified mechanism for access validation within the event-types module.
apps/api/v2/src/modules/event-types/services · high confidence
Conferencing settings page now uses server-side data fetching
The My Account \> Conferencing settings page has been updated to fetch data on the server, improving load performance. The page component now directly calls TRPC routers to retrieve installed conferencing integrations, the user's default conferencing app, and event type data before rendering the view. A new loading state component has been added to display a skeleton loader while this data is being fetched.
apps/web/app/(use-page-wrapper)/settings/(settings-layout)/my-account/conferencing · high confidence
Daily webhook handler refactored to use repositories and new webhook events
The daily webhook handler in apps/web/lib/daily-webhook has been refactored to improve data access and expand event coverage. Data retrieval for bookings and references now uses dedicated repositories (BookingRepository, BookingReferenceRepository) instead of direct Prisma calls, enhancing maintainability. Additionally, the system now supports triggering webhooks for RECORDING\_READY and RECORDING\_TRANSCRIPTION\_GENERATED events, allowing subscribers to react when recordings and transcriptions are ready.
apps/web/lib/daily-webhook · high confidence
Decouple tRPC React layer and introduce PBAC procedure middleware
The tRPC package has been restructured to separate client-side React exports from the server-side implementation, requiring client code to import from \@calcom/trpc/react\ instead of \@calcom/trpc\ to improve build performance. Additionally, the package now includes a new PBAC (Permission-Based Access Control) procedure layer (\pbacProcedures.ts\) that enforces team and organization-level permissions, alongside new error conversion middleware to standardize error handling across tRPC routes.
packages/trpc · high confidence
Deduplicate city options by population to prevent timezone confusion
The city selection dropdown now filters out duplicate city names, retaining only the entry with the highest population. This change prevents users from seeing multiple options for the same city name with potentially different timezones, ensuring the most populated city's timezone is selected by default. Additionally, specific overrides are applied, such as mapping 'Londonderry' to 'London' and ensuring 'London' uses the 'Europe/London' timezone.
packages/features/cityTimezones · high confidence
Deprecated OAuth client managed user endpoints
The API v2 endpoints for managing OAuth client users (GET, POST, PATCH, DELETE, and force-refresh) are now marked as deprecated. These endpoints, located at /v2/oauth-clients/:clientId/users, allow administrators and owners to create, retrieve, update, and delete managed users, as well as force-refresh their access and refresh tokens. The API responses include user details along with token information (access token, refresh token, and their expiration times). Users should prepare for these endpoints to be removed in a future version.
apps/api/v2/src/modules/oauth-clients/controllers/oauth-client-users · high confidence
Deprecated Platform OAuth Client Webhooks API endpoints
The API v2 endpoints for managing webhooks on platform OAuth clients (POST, GET, PATCH, DELETE at /v2/oauth-clients/:clientId/webhooks) are now officially marked as deprecated. These endpoints, which allow platform administrators and owners to create, update, retrieve, and delete webhooks associated with an OAuth client, will be removed in a future release. Users should prepare to migrate to the new webhook management system.
apps/api/v2/src/modules/oauth-clients/controllers/oauth-client-webhooks · high confidence
Deprecated Platform OAuth Client endpoints in API v2
The OAuth client management endpoints in the API v2 module are now officially marked as deprecated. The controller and its associated end-to-end tests explicitly tag these routes with a deprecation warning, indicating they will be removed in a future release. This change affects the ability to create, read, update, and delete OAuth clients via the v2 API, signaling that users should migrate to alternative platform integration methods.
apps/api/v2/src/modules/oauth-clients/controllers/oauth-clients · high confidence
Email system refactored to use JSX templates and modular service files
The email system has been refactored to use JSX as the templating engine, replacing the previous approach. This change introduces a new modular structure with dedicated service files for different email categories (auth, billing, daily video, integration, OAuth, organization, and recording) and a centralized \email-manager.ts\ for booking-related notifications. The refactoring also includes improved ICS file generation with better handling of organizer email privacy, consistent iCalUIDs, and proper method status for cancellations, along with added tests for attendee email filtering and ICS generation.
packages/emails · high confidence
Enable experimental agent teams feature
The .claude directory has been restructured to consolidate agent configuration into a dedicated agents directory, with the rules and skills directories now acting as symlinks to ../agents/rules and ../agents/skills respectively. Additionally, the experimental agent teams feature is enabled by setting the CLAUDE\_CODE\_EXPERIMENTAL\_AGENT\_TEAMS environment variable to 1 in the settings.json file.
.claude · medium confidence
Enforce event-type ownership via new API guard
A new EventTypeOwnershipGuard has been added to the v2 API to ensure that users can only access event types they own. When a request includes an eventTypeId, the guard validates the parameter and checks ownership against the user's account, returning a 404 if the event type is not found or not owned, and a 403 if no user is associated with the request.
apps/api/v2/src/modules/event-types/guards · high confidence
Event types page migrated to Next.js App Router
The event types listing page has been rebuilt using the Next.js App Router, introducing server-side data fetching via tRPC with one-hour caching, client-side search debouncing, and dedicated loading/error states. The new structure includes a server component for initial data retrieval and onboarding redirects, a client wrapper for search context, and a revalidation action to keep the list fresh after changes.
apps/web/app/(use-page-wrapper)/(main-nav)/event-types, apps/web/app/(use-page-wrapper)/auth/logout, apps/web/app/(use-page-wrapper)/getting-started · high confidence
Extracted app data management into a dedicated hook
The \useAppsData\ hook has been moved into the \packages/features/apps/hooks\ directory, centralizing the logic for reading and writing application-specific metadata within the event type form. This change isolates the form state management for apps, making the codebase easier to maintain and reducing coupling between the app store and library components.
packages/features/apps/hooks · high confidence
Form builder field configuration and prefill logic restructured
The form builder now uses a centralized configuration map (\fieldTypesConfigMap\) to define field properties, supporting variants (such as splitting the name field into first and last name) and safe HTML rendering for labels. Additionally, the prefill behavior has been refined: fields with the 'disableOnPrefill' option are now disabled only when the prefilled value matches the current response, and they are re-enabled if the user modifies the field or if validation errors occur for that specific field.
packages/features/form-builder · high confidence
Formbricks integration moved to web module with custom feedback dialog support
The Formbricks hooks and stores have been relocated from the shared packages to the apps/web/modules/formbricks directory, centralizing the integration within the web application. This change includes the implementation of a custom feedback dialog for feature opt-in, allowing users to provide specific feedback on new features. The integration now initializes Formbricks with user attributes (name, email, username, team membership, and organization admin status) and supports tracking custom actions via the trackFormbricksAction utility.
apps/web/modules/formbricks · high confidence
Implement server-side props for email change verification
The email change verification flow now uses a dedicated \getServerSideProps\ function to handle token validation and API communication on the server. This ensures that the verification token is securely passed to the backend API endpoint, and the resulting session update status is passed as props to the page component, improving reliability and security for users completing the email change process.
apps/web/server/lib/auth/verify-email-change · high confidence
Improved calendar event descriptions and new error handling classes
The \CalEventParser\ now sanitizes calendar event descriptions by skipping null or empty booking question values (preventing the literal string "null" from appearing) and converting HTML descriptions to plain text while preserving line breaks and links. Additionally, new \CalendarAppError\ classes have been introduced to handle delegation credential issues, and tests have been added for the \CalEventParser\, \CalendarService\ (UID consistency and VTIMEZONE generation), and \OgImages\ (versioning and branding).
packages/lib · high confidence
Improved calendar subscription batch processing with error handling and filtering
The selected calendar repository now implements more robust logic for finding the next batch of calendars to subscribe. It skips calendars with recent subscription errors (within the last 24 hours) and entirely excludes those with three or more errors. Additionally, it now supports filtering out generic calendars by suffix and correctly joins with team memberships to include calendars for users in specific teams. These changes improve the reliability and scope of calendar subscription updates.
packages/features/selectedCalendar · high confidence
Improved theme persistence and email verification reliability
The email verification page now handles secondary email updates and auto-joining organizations more robustly, ensuring users are redirected to the correct onboarding or event-types path after verification. Additionally, a new document theme application utility ensures that booking-specific themes are correctly applied on the client side, even when localStorage access is restricted or errors occur, improving the visual consistency of booking pages.
apps/web/lib/pages · high confidence
Introduce Onboarding V3 with server-side routing and feature flag gating
The onboarding flow has been updated to version 3, introducing new server-side pages for the getting-started, personal profile, personal calendar, and personal settings steps. A new layout at the onboarding root now gates access to this flow behind the 'onboarding-v3' feature flag, redirecting users to the legacy '/getting-started' page if the flag is disabled. The getting-started page includes logic to detect existing team memberships and redirect users directly to personal settings, while the personal settings page now accepts a 'fromTeamOnboarding' search parameter to handle post-invite onboarding paths.
apps/web/app/(use-page-wrapper)/onboarding · high confidence
Introduce calendar subscription cache cleanup cron and restructure web app configuration
The web application now includes a new scheduled task to clean up stale calendar subscription cache, exposed via the \/api/cron/calendar-subscriptions-cleanup\ endpoint and secured by API key or Bearer token checks. This is supported by a new \cron-tester.ts\ utility for local testing and updated Vercel cron configurations. Additionally, the app's configuration has been restructured: the Next.js configuration is now written in TypeScript (\next.config.ts\), PostCSS is configured for Tailwind v4, and shadcn/ui is initialized with the \coss-ui\ package. Organization domain routing logic has been extracted into dedicated helper files (\getNextjsOrgRewriteConfig.ts\, \pagesAndRewritePaths.ts\), and Sentry instrumentation is now explicitly configured for client, server, and edge environments with specific error filtering.
apps/web · high confidence
Introduce dedicated route layouts for booking and general use pages
New layout components have been added for the \(booking-page-wrapper)\ and \(use-page-wrapper)\ route groups to standardize how page wrappers and scripts are rendered. The booking layout now explicitly passes \isBookingPage={true}\ and \requiresLicense={false}\ to the \PageWrapper\, ensuring booking pages are handled correctly without license checks. The general use layout injects head and body scripts from environment variables (\NEXT\_PUBLIC\_HEAD\_SCRIPTS\, \NEXT\_PUBLIC\_BODY\_SCRIPTS\) into the page, applying the CSP nonce to these injected scripts for security compliance.
apps/web/app/(use-page-wrapper) · high confidence
Introduce dedicated worker thread for available slots calculation
A new NestJS-based worker module and entry point have been added to offload the \getAvailableSlots\ operation into a separate Node.js worker thread. This change prevents CPU-intensive slot availability calculations from blocking the main API event loop, ensuring that other requests continue to be processed without latency spikes. The worker bootstraps a minimal NestJS application context, injects the \AvailableSlotsService\, and communicates with the main thread via message passing to execute the slot queries.
apps/api/v2/src/modules/slots/slots-2024-04-15/workers · high confidence
Introduces UsersService for centralized user profile resolution logic
A new UsersService has been added to the v2 API users module to centralize logic for resolving user profiles and organization IDs. This service provides methods to fetch users by username, identify a user's main profile (prioritizing the moved-to profile, then the profile matching the user's organization ID, and finally the first available profile), retrieve the main organization ID, and find a specific profile by organization ID. This refactoring consolidates profile resolution logic previously scattered across the codebase into a single, reusable service.
apps/api/v2/src/modules/users/services · high confidence
License key page now supports Dub.co conversion tracking
The license key settings page now captures and passes Dub.co tracking identifiers (specifically \dub\_id\, with fallback to the legacy \dclid\ cookie) to the authentication session. This enables conversion tracking for users accessing this admin-only route, aligning it with the broader implementation of Dub.co for tracking across the application.
apps/web/lib/settings · high confidence
Localize country flag assets for phone input
Country flag SVG icons are now served from the local public folder instead of an external domain. This change ensures that flags used by the react-phone-number-input component load reliably without depending on third-party hosting, improving privacy and reducing external network requests.
apps/web/public/country-flag-icons · high confidence
Maintenance page now uses client-side rendering with internationalization
The maintenance page has been migrated to the App Router and converted into a client component. This change enables the use of the \useLocale\ hook, ensuring that the page title, message, and support button text are properly translated for users based on their language preferences, rather than displaying hard-coded strings.
apps/web/modules/maintenance · high confidence
Meeting ended page now uses server-side props with a booking DTO
The meeting ended page now fetches booking data via a new \getServerSideProps\ file that instantiates a \BookingRepository\ to retrieve the booking. To prevent sensitive data leakage, the booking object passed to the page is now a Data Transfer Object (DTO) containing only the title, start time, and end time, rather than the full database record.
apps/web/lib/video/meeting-ended · high confidence
Migrate /more page to App Router
The /more page has been migrated to the App Router, replacing the previous implementation with a new client-side view component. This change updates the page structure to use the shared Shell layout and MobileNavigationMoreItems, ensuring consistent navigation and layout behavior within the new routing architecture.
apps/web/modules/more · high confidence
Migrate OAuth API routes to the Next.js App Router
The OAuth authentication endpoints, specifically the refresh token and 'me' (user info) routes, have been migrated from the legacy Pages Router to the new App Router structure. This change updates the underlying request handling mechanism to use Next.js App Router conventions (e.g., \route.ts\ files with named HTTP method exports like \GET\/\POST\) and integrates with the new \defaultResponderForAppDir\ wrapper. For users, this ensures consistent API behavior and performance improvements associated with the App Router, while maintaining the same OAuth token refresh and profile retrieval functionality.
apps/web/app/api/auth/oauth/refreshToken · high confidence
Migrate app category pages to the new module structure
The app store category listing and individual category view pages have been moved into the new \apps/web/modules/apps/categories\ directory. This change updates the underlying component implementation to use the new module-based routing and layout structure, ensuring these specific pages are consistent with the broader application router migration while preserving the existing user-facing functionality of browsing and filtering apps by category.
apps/web/modules/apps/categories · high confidence
Migrate apps/\[slug\] pages to the App Router
The \/apps/\[slug\]\ and \/apps/\[slug\]/setup\ routes have been migrated to the Next.js App Router. This introduces new client-side components (\slug-view.tsx\ and \setup-view.tsx\) that handle app display logic, including error notifications for linked accounts or missing calendars, and manages authentication redirects for the setup flow. The migration also updates the setup page to use \useCompatSearchParams\ for URL handling and ensures the app setup page correctly passes props from the server-side data fetching logic.
apps/web/modules/apps/\[slug\] · high confidence
Migrate auth API routes to App Router with CSRF protection
The password reset and initial setup API endpoints have been migrated to the Next.js App Router structure. This change introduces CSRF token validation for the password reset flow to prevent unauthorized submissions, implements stricter input validation using Zod schemas, and ensures consistent error handling and rate limiting across these authentication endpoints.
apps/web/app/api/auth/reset-password · high confidence
Migrate booking cancellation to App Router with enhanced security
The booking cancellation endpoint has been moved to the App Router (\/api/cancel/route.ts\), introducing stricter validation that requires a high-entropy \uid\ instead of integer IDs to prevent guessing attacks. The new route also enforces CSRF protection and implements rate limiting (10 cancellations per 60 seconds) to protect against abuse, while maintaining compatibility with the existing cancellation logic.
apps/web/app/api/cancel · high confidence
Migrate calendar availability API to Next.js App Router
The calendar availability endpoint has been moved from the legacy Pages Router to the new App Router structure (apps/web/app/api/availability/calendar/route.ts). This change updates the API implementation to use Next.js App Router conventions, including the use of \defaultResponderForAppDir\ for response handling and \next/headers\ for request context. The endpoint retains its existing functionality for retrieving, selecting, and deleting user calendar integrations, ensuring backward compatibility for clients consuming this API.
apps/web/app/api/availability · high confidence
Migrate forgot-password pages to Next.js App Router
The forgot-password flow has been migrated from the legacy pages directory to the Next.js App Router. This introduces new server components at /auth/forgot-password and /auth/forgot-password/\[id\] that handle server-side rendering, metadata generation, and session checks (redirecting authenticated users away from the reset page) using the new Next.js headers/cookies APIs and the buildLegacyCtx adapter to bridge with existing server-side logic.
apps/web/app/(use-page-wrapper)/apps/categories, apps/web/app/(use-page-wrapper)/auth/forgot-password, apps/web/app/reschedule · high confidence
Migrate installed apps pages to the new app router structure
The installed apps interface has been restructured to use the new Next.js app router. The main view for installed apps is now located at \apps/web/modules/apps/installed/\[category\]/installed-category-view.tsx\, which renders the list of installed integrations, handles disconnection logic, and manages default conferencing app settings. This change moves the page implementation from the previous pages directory into the modules structure, aligning with the broader app-router migration for the \/apps\ section.
apps/web/modules/apps/installed · high confidence
Migrate login page to Next.js App Router with server-side logic
The login page logic has been migrated from the legacy Pages Router to the App Router by introducing a new \getServerSideProps.tsx\ file. This change implements server-side checks for existing sessions and user existence (redirecting new installations to setup), validates JWT tokens for TOTP flows, and passes CSRF tokens and login provider flags to the client component.
apps/web/server/lib/auth/login · high confidence
Migrate signin page to Next.js App Router
The signin page has been migrated from the Pages Router to the App Router. The previous server-side data fetching logic using \getServerSideProps\ has been removed and replaced with a new implementation compatible with the App Router architecture, ensuring the page continues to fetch CSRF tokens and authentication providers on the server side.
apps/web/server/lib/auth/signin · high confidence
Migrate signup API to Next.js App Router
The signup API has been migrated from the Pages Router to the App Router structure, now located at apps/web/app/api/auth/signup/route.ts. This change introduces improved error handling for rate limiting and Cloudflare Turnstile verification, ensures signup availability is checked against feature flags, and supports UTM tag storage via Stripe during the signup process. The route now uses dependency injection for the FeaturesRepository and handles both Cal.com and self-hosted signup flows based on configuration.
(repo-wide) · high confidence
Migrate two-factor authentication API routes to the Next.js App Router
The two-factor authentication endpoints (TOTP setup, enable, and disable) have been migrated from the legacy Pages Router to the Next.js App Router. This change updates the API structure to use the new \route.ts\ file convention and integrates with the application's App Router-specific request handling and error wrapping, ensuring consistent behavior for users managing their two-factor security settings.
apps/web/app/api/auth/two-factor · high confidence
Migrate user and type booking pages to App Router with SEO and i18n support
The user profile and event type booking pages have been migrated to the Next.js App Router within the (booking-page-wrapper) route group. This change introduces server-side rendering for these pages, enabling dynamic SEO metadata generation that respects user and organization-level indexing preferences (controlling robots follow/index directives). Additionally, the embed variants of these pages are now explicitly configured to prevent search engine indexing, and the main pages support interface language localization via the new @calcom/i18n package, ensuring translations are loaded and provided contextually for the booking experience.
apps/web/app/(booking-page-wrapper)/\[user\] · high confidence
Migrate video and signup pages to Next.js App Router
The video and signup pages have been converted from the legacy Pages Router to the Next.js App Router. This change introduces server components for routes like /video/\[uid\], /video/meeting-ended/\[uid\], /video/meeting-not-started/\[uid\], /video/no-meeting-found, and /signup, utilizing the new \withAppDirSsr\ wrapper and \buildLegacyCtx\ to bridge legacy data-fetching logic. Users will experience these pages loading as server-rendered components, with the /video/meeting-not-started route now performing direct database queries via \BookingRepository\ to generate metadata.
apps/web/app/(use-page-wrapper)/video · high confidence
Migrated OG image generation API to App Router with caching
The social OG image generation endpoint has been moved to the App Router (\/api/social/og/image/route.tsx\), replacing the previous Pages Router implementation. This change introduces robust input validation via Zod schemas for meeting, app, and generic image types, and implements aggressive HTTP caching (1-year immutable cache with ETags) to improve performance. The API now supports generating images for meetings, apps (including SVG hash lookups), and generic content, ensuring consistent error handling and response formats.
apps/web/app/api/social/og/image · high confidence
Migrated app detail and setup pages to Next.js App Router
The app detail page (\/apps/\[slug\]\) and the app setup page (\/apps/\[slug\]/setup\) have been migrated to the Next.js App Router. The app detail page now uses server components to fetch static props and generate metadata, while the setup page wraps legacy server-side logic using \withAppDirSsr\ and \buildLegacyCtx\ to maintain compatibility with existing data fetching patterns.
apps/web/app/(use-page-wrapper)/apps/\[slug\] · high confidence
Migrated forgot-password API to App Router with enhanced security and rate limiting
The forgot-password API route has been migrated to the Next.js App Router, introducing a new handler that uses \parseRequestData\ for request body parsing and \defaultResponderForAppDir\ for response handling. This change implements IP-based rate limiting using a hashed identifier to protect against abuse while preserving user privacy, and ensures the endpoint does not leak information about whether a user account exists by returning a generic success message regardless of the user's presence in the database.
apps/web/app/api/auth/forgot-password · high confidence
Migration of installation onboarding to Next.js App Router
The installation onboarding flow has been migrated from the legacy Pages Router to the Next.js App Router. The new \page.tsx\ implementation uses server components to fetch data via \withAppDirSsr\ and \buildLegacyCtx\, ensuring the installation wizard continues to function correctly while leveraging the modern routing and rendering architecture.
apps/web/app/(use-page-wrapper)/apps/installation · high confidence
My Account settings pages now use server-side rendering with loading states
The Appearance, General, and Profile pages within My Account settings have been converted to server components. This change introduces dedicated loading skeletons for each page to improve perceived performance and adds server actions to handle path revalidation after updates, ensuring the UI stays in sync with data changes.
apps/web/app/(use-page-wrapper)/settings/(settings-layout)/my-account/appearance, apps/web/app/(use-page-wrapper)/settings/(settings-layout)/my-account/general, apps/web/app/(use-page-wrapper)/settings/(settings-layout)/my-account/profile · high confidence
New API request parsing and error handling utilities for App Router
This change introduces \defaultResponderForAppDir\ and \parseRequestData\ within the \apps/web/app/api\ directory to standardize how API routes handle requests and errors. \parseRequestData\ now explicitly parses JSON, URL-encoded, and multipart form data using \req.formData()\ and \req.text()\, ensuring correct handling of various content types that Next.js does not parse automatically. \defaultResponderForAppDir\ provides a wrapper for API handlers that automatically manages error responses, mapping TRPC and API errors to appropriate HTTP status codes (including 409 for specific business errors and 429 for rate limits) and conditionally reporting non-client errors to Sentry.
apps/web/app/api · high confidence
New client-side onboarding view for Getting Started
The Getting Started module now uses a new client-side component (\onboarding-view.tsx\) to manage the multi-step onboarding flow. This view handles navigation between steps (User Settings, Connected Calendar, Connected Video, Setup Availability, and User Profile) using Next.js App Router conventions and React transitions. It integrates PostHog for tracking step completions and displays a loading state via \LoaderIcon\ while steps are processing. The component also includes a Toaster from Sonner for notifications and uses specific CSS variables for theming the onboarding interface.
apps/web/modules/getting-started · high confidence
New credential deletion logic and access control services
The credentials feature now includes a dedicated \handleDeleteCredential\ handler that automatically cleans up integrations when a credential is removed: video/conferencing credentials are replaced with Cal Video, calendar credentials remove associated destination calendars, CRM credentials hide the event type, and payment credentials hide the event type, zero out the price, and soft-delete related booking references. A new \CredentialAccessService\ enforces strict access control, ensuring credentials are only accessible by the owner, the booking owner, or users within the same team or organization. These capabilities are backed by a new \CredentialRepository\ for data access and a DI module for dependency injection.
packages/features/credentials · high confidence
New global styles and query-builder UI overrides
This change introduces new global CSS rules for the web application, including Tailwind v4 compatibility utilities (stack-y-\*), desktop app-specific styling for ToDesktop (vibrancy, drag regions, user-select), and custom focus ring colors for form inputs. It also adds a new raqb.css file that overrides the styling for the react-query-awesome-builder component, hiding connectors and drag handlers while enforcing a specific layout for query rules.
apps/web/styles · high confidence
New input DTOs for email verification and event type atoms
This change introduces a set of new input Data Transfer Objects (DTOs) within the v2 API atoms module to support specific booking and verification workflows. For email verification, it adds \AddVerifiedEmailInput\, \CheckEmailVerificationRequiredParams\, \GetVerifiedEmailsParams\, \GetVerifiedEmailsInput\, \SendVerificationEmailInput\, and \VerifyEmailCodeInput\, which define the required fields (such as email, code, username, and language) for sending and verifying email codes. Additionally, it adds \EventTypesAppInput\ and \BulkUpdateEventTypeToDefaultLocationDto\ for managing event type attributes, and query parameter classes (\GetAtomPublicEventTypeQueryParams\, \GetAtomSchedulesQueryParams\) to handle filtering for public event types and schedules.
apps/api/v2/src/modules/atoms/inputs · high confidence
New layout components for Apps and Installed Apps sections
The Apps and Installed Apps sections now use dedicated layout components (AppsLayout and InstalledAppsLayout) that wrap content in the Shell. AppsLayout introduces an empty state screen for when no external apps are configured, displaying different messages for admin and non-admin users, and includes navigation to the admin settings. InstalledAppsLayout adds a category navigation component to help users browse their installed apps.
apps/web/components/apps/layouts · high confidence
New scheduling components and hooks relocated to apps/web/modules/schedules
The scheduling UI and logic previously located in packages/features have been moved into a new dedicated module at apps/web/modules/schedules. This relocation introduces a NewScheduleButton component for creating schedules, a Schedule wrapper component, and a suite of hooks (useEvent, useSchedule, useApiV2AvailableSlots, useNonEmptyScheduleDays, useSlotsForDate) that manage event data, availability fetching (including API v2 support for team events), and slot caching. A test file for DateOverrideList is also included in this location to verify time-format rendering.
apps/web/modules/schedules · high confidence
New server-fetched booking page component with error handling
A new \d-type-view.tsx\ component has been added for the \/d/\[link\]\ route, wrapping the Booker in a \BookingPageErrorBoundary\ to improve resilience during booking flows. This component consumes server-side props (such as \eventData\, \booking\, and \user\) and passes them to the \BookerWebWrapper\, aligning with the shift toward server-fetched data for instant-meeting and private booking pages.
apps/web/modules/d · high confidence
New server-side email verification page
A new page component has been added at /auth/verify-email to handle email verification. This page is implemented as a server component that wraps the existing client-side VerifyEmailPage view, ensuring compliance with React Server Components (RSC) best practices by avoiding the export of client components as default exports. The page also includes metadata generation for SEO and accessibility purposes.
apps/web/app/(use-page-wrapper)/auth/verify-email · high confidence
New status-based bookings page with feature-flagged v3 support
A new dynamic route at \[status\]/page.tsx now serves bookings filtered by status (e.g., upcoming, past), replacing the previous static structure. This page checks the 'bookings-v3' feature flag to conditionally render the v3-enabled BookingsList component or fall back to the legacy view, and only displays the page heading/subtitle when v3 is disabled. It also enforces authentication and validates the status parameter against allowed values, redirecting to /bookings/upcoming if invalid.
apps/web/app/(use-page-wrapper)/(main-nav)/bookings · high confidence
New user profile validation rules for avatars, locale, and display preferences
The API now enforces stricter validation on user profile settings. Avatar uploads are restricted to HTTPS URLs or base64-encoded image data (PNG, JPEG, GIF, WEBP), blocking insecure HTTP, FTP, file, and javascript protocols to prevent XSS. User preferences for locale, theme (dark/light), time format (12/24h), and time zone are now validated against specific allowed values or standard system formats, ensuring consistent data integrity for user display settings.
apps/api/v2/src/modules/users/validators · high confidence
New v2 slots service with worker thread support and output formatting
The v2 slots module (2024-04-15) now includes dedicated services for handling slot availability and reservation. A new SlotsWorkerService introduces a configurable pool of Node.js worker threads to perform slot calculations off the main thread, preventing CPU blocking and ensuring failed workers are automatically terminated and replaced. The SlotsOutputService handles the transformation of raw slot data, supporting both 'time' and 'range' formats and applying timezone conversions. Additionally, the SlotsService manages slot reservations, including logic for handling seated events with limited capacity and dry-run modes.
apps/api/v2/src/modules/slots/slots-2024-04-15/services · high confidence
OAuth client access validation in API v2
The API v2 now enforces that users can only access OAuth clients belonging to their organization, with an exception for system administrators. This guard validates the client ID, ensures an organization context exists, and rejects requests with a 403 Forbidden error if the client does not match the user's primary organization or if the user lacks admin privileges.
apps/api/v2/src/modules/oauth-clients/guards · high confidence
OAuth token endpoint migrated to App Router with PKCE support
The OAuth token exchange endpoint has been moved to the Next.js App Router as a new route file. This change introduces support for PKCE (Proof Key for Code Exchange) by accepting and validating the \code\_verifier\ parameter during the token exchange process. The endpoint now uses \parseUrlFormData\ to handle request data and returns standard OAuth2 response fields including \token\_type\ and \expires\_in\. It also includes a check for the \CALENDSO\_ENCRYPTION\_KEY\ environment variable, returning a 500 error if missing.
apps/web/app/api/auth/oauth/token · high confidence
OAuth2 service refactored with PKCE support and developer testing for pending clients
The OAuth2 backend logic has been restructured into a dedicated \OAuthService\ with repository-based data access, introducing support for PKCE (Proof Key for Code Exchange) for public clients and allowing owners to authorize their own OAuth clients while they are in a PENDING state for testing purposes. Previously, only APPROVED clients could be used for authorization; now, the service explicitly permits PENDING clients owned by the requesting user, while still blocking REJECTED clients, and enforces PKCE requirements (S256 challenge) for PUBLIC client types during authorization code generation.
packages/features/oauth · high confidence
Onboarding redirects now respect the onboarding-v3 feature flag
The onboarding path service now dynamically determines the correct starting URL based on the global 'onboarding-v3' feature flag. When the flag is enabled, users are directed to the new onboarding flow (e.g., /onboarding/getting-started or /onboarding/personal/settings for invite links); otherwise, they are redirected to the legacy paths (/getting-started). This ensures a seamless transition for users as the new onboarding experience is rolled out.
packages/features/onboarding · high confidence
Optional API Auth Guard now accepts partial credentials
The OptionalApiAuthGuard has been updated to gracefully handle scenarios where only a client ID or only a client secret is provided during authentication. Previously, providing just one of these credentials would likely result in an authentication error; now, the guard recognizes these specific partial-credential states and treats them as valid 'no user' outcomes (returning null), allowing the request to proceed without a user context while still throwing errors for other invalid authentication attempts.
apps/api/v2/src/modules/auth/guards/optional-api-auth · high confidence
Paginated host and team member endpoints for large teams
The host feature now supports paginated queries for retrieving hosts and team members, addressing performance issues with large teams. New repository methods and service endpoints (\getHostsForAvailability\, \getHostsForAssignment\, \getChildrenForAssignment\, \searchTeamMembers\) return cursor-based pagination results, allowing users to efficiently browse hosts and team members without loading entire datasets into memory.
packages/features/host · high confidence
Patch updates for Prisma, dayjs, libphonenumber-js, and next-i18next
This change applies four patches to dependencies in the Yarn PnP store. The @prisma-client patch modifies runtime/binary.js and runtime/library.js to adjust environment conflict checking behavior (changing conflictCheck from "warn" to "none" in specific code paths). The dayjs patches (for versions 1.11.2 and 1.11.4) update the timezone plugin to use Object.assign for merging configuration objects and standardize Intl.DateTimeFormat options. The libphonenumber-js patch comments out legacy named export assignments in index.cjs. The next-i18next patch removes the import of appWithTranslation and disables the reloadResources call in serverSideTranslations, effectively bypassing the global i18n reload logic during server-side translation initialization.
.yarn/patches · high confidence
Permissions guard now skips validation for third-party OAuth tokens
The permissions guard in the API v2 authentication module has been updated to bypass permission checks for third-party OAuth access tokens. Previously, these tokens might have triggered permission validation errors; now, if a bearer token is identified as a third-party token, the guard immediately allows access without verifying specific OAuth client permissions, while still enforcing checks for managed platform OAuth clients and API keys.
apps/api/v2/src/modules/auth/guards/permissions · high confidence
Pre-commit hook skips linting during merges and runs store generation
The pre-commit hook now detects when a merge is in progress (by checking for .git/MERGE\_HEAD) and skips lint-staged and generator tasks to avoid conflicts. For normal commits, it runs lint-staged and executes the app-store build, automatically staging the generated files in packages/app-store/.
.husky · high confidence
Prisma client refactored with new extensions and connection pooling
The Prisma client initialization in \packages/prisma\ has been refactored to support connection pooling via \@prisma/adapter-pg\ and to enforce stricter data integrity through new Prisma extensions. The client now automatically excludes locked users from queries, prevents teams with pending payments from being returned, and manages booking idempotency keys based on status changes. Additionally, it blocks \deleteMany\ and \updateMany\ operations that contain undefined values in their \where\ clauses to prevent accidental data loss. The client also supports a separate read-only instance for insights using \INSIGHTS\_DATABASE\_URL\.
packages/prisma · high confidence
Profile branding and security logic moved to dedicated feature module
The profile feature now includes dedicated logic for handling organization-level branding inheritance and security checks. Users will see consistent organization brand colors and themes applied to personal and team events, with proper fallbacks to user or team settings when organization branding is not configured. Additionally, the profile access system has been hardened with UUID-based identifiers and strict cross-tenant isolation, preventing users from accessing profiles outside their organization. The codebase has also been restructured to use dedicated repositories for profile data access, improving maintainability and removing circular dependencies.
packages/features/profile · high confidence
Redesigned webhooks management interface with new UI components
The webhooks settings page has been completely rebuilt using the new @coss/ui component library, replacing the previous implementation. This update introduces a modernized list view that groups webhooks by team or user profile, featuring inline toggles to activate or deactivate webhooks and a dedicated delete confirmation dialog. The creation and editing workflows now utilize a unified form component with a new version selector (WebhookVersionCTA) and an integrated test trigger panel (WebhookTestDisclosure) for validating webhook configurations. Additionally, a new 'Create New Webhook' button allows users to select the target team or profile before navigating to the creation form.
apps/web/modules/webhooks · high confidence
Redirects enterprise page and adds maintenance page
The enterprise page now redirects users to the home page, resolving a client-export warning. Additionally, a new maintenance page has been added that displays a legacy maintenance view and generates appropriate metadata for the under-maintenance state.
apps/web/app/(use-page-wrapper)/enterprise · high confidence
Refactored availability logic with new holiday blocking and schedule detection
The availability feature has been significantly refactored to improve accuracy and performance. A new Holidays feature now blocks availability on public holidays, with tests verifying that holidays are correctly applied to working days and skipped on non-working days. The \detectEventTypeScheduleForUser\ function was introduced to prioritize schedules from event types, hosts, or user defaults, ensuring correct timezone handling. Availability aggregation logic was updated to properly handle fixed and round-robin hosts, merging overlapping date ranges and filtering redundant ones to prevent erroneous slot generation. Additionally, a \SkeletonLoader\ component was added to improve the user experience during availability loading.
packages/features/availability · high confidence
Refactored busy times calculation into a service with batched limit checks
The busy times logic in the \busyTimes\ feature has been restructured into a \BusyTimesService\ with dedicated integration and unit tests. A key behavioral change is the introduction of batched parallel queries for limit checks (\getBusyTimesForLimitChecks\), which processes user lists in batches of 50 with a concurrency limit of 5 to improve performance. The service now explicitly handles reschedule UIDs to exclude them from busy time results and manages booking/duration limits using a \LimitManager\.
packages/features/busyTimes · high confidence
Refactored username availability component to separate premium and standard flows
The username availability UI has been restructured into two distinct components: \PremiumTextfield\ and \UsernameTextfield\, selected dynamically based on the user's premium status. This change isolates the premium username logic—such as payment requirements, reservation flows, and specific error messaging for unpaid premium attempts—from the standard username validation logic. The refactoring ensures that non-premium users see a simplified interface without premium-specific prompts, while premium users are guided through the necessary payment and reservation steps for exclusive usernames.
apps/web/components/ui/UsernameAvailability · high confidence
Removal of default Next.js starter styles
The default CSS styles provided by the initial Next.js project setup have been removed. Specifically, the \styles/Home.module.css\ file, which contained layout and card styling for the home page, and the \styles/globals.css\ file, which defined global resets and font families, are no longer present in the codebase. This indicates a shift away from the default template styling, likely to allow for custom or framework-specific styling solutions.
styles · high confidence
Render markdown in custom page redirect messages
The router's embed and index pages now support rich text formatting in custom redirect messages. By importing and using the \markdownToSafeHTML\ utility, the \index.tsx\ component sanitizes incoming \message\ or \errorMessage\ props and renders them as HTML via \dangerouslySetInnerHTML\. This allows users to include formatted content (such as bolding or lists) in their custom router redirect messages, which is then displayed safely in the embed view.
apps/web/pages/router · high confidence
Restores and enhances custom error handling and document structure for the Pages Router
This change restores the Next.js Pages Router entry points (\\_app.tsx\, \\_document.tsx\, \\_error.tsx\) which were previously removed or modified. It re-introduces a custom error page that redacts sensitive Prisma errors and properly handles HTTP errors, ensuring users see a consistent UI instead of raw stack traces. The document setup now correctly initializes locale and directionality attributes on the HTML tag and applies theme styles via inline scripts, while the app wrapper ensures Session and Web Push providers are available across all pages. This restores the foundational structure required for the pages router to function correctly with proper i18n, theming, and error reporting.
apps/web/pages · high confidence
Role-based access control with caching and PBAC integration
The API v2 now uses a new RolesGuard to enforce minimum required roles for organizations and teams. This guard supports PBAC-authorized requests by skipping legacy role checks when the request is already authorized. It caches role access decisions in Redis for 300 seconds to improve performance. The guard distinguishes between organization and team roles, ensuring that organization-level permissions take precedence over team-level ones. System admins are granted access to all resources, while non-admin users must meet the minimum role requirements for the specific organization or team context.
apps/api/v2/src/modules/auth/guards/roles · high confidence
Server-side data fetching for the new webhook creation page
The new webhook creation page now fetches required data (installed apps and existing webhooks) on the server side before rendering. This change introduces a new page component that uses tRPC to retrieve the necessary context and passes it to the view, along with a dedicated loading state component to improve perceived performance and ensure data availability before the form is displayed.
apps/web/app/(use-page-wrapper)/settings/(settings-layout)/developer/webhooks/new · high confidence
Server-side logic for user booking pages now supports rescheduling cancelled bookings
The server-side props handler for user booking pages has been updated to support rescheduling cancelled bookings when the \allowRescheduleForCancelledBooking\ query parameter is present. This allows users to proceed with rescheduling even if the original booking status is cancelled, provided the event type does not explicitly disable rescheduling. The logic also handles redirects to the original event link if rescheduling is not permitted or if the booking is invalid.
apps/web/server/lib/\[user\]/\[type\] · high confidence
Server-side rendering and caching for the API Keys settings page
The API Keys page in Developer Settings has been migrated to a Server Component, enabling server-side data fetching and improved performance. The page now uses Next.js \unstable\_cache\ to cache the list of API keys for one hour, tagged for efficient invalidation. A new server action (\revalidateApiKeysList\) allows the cache to be cleared when keys are updated. A dedicated loading state using a skeleton loader has also been added to improve perceived performance during data retrieval.
apps/web/app/(use-page-wrapper)/settings/(settings-layout)/developer/api-keys · high confidence
Server-side rendering and caching for the event type edit page
The event type edit page (apps/web/app/(use-page-wrapper)/event-types/\[type\]) has been migrated to a Server Component architecture. The page now fetches event type data via a cached tRPC query (revalidating every hour) and enforces authentication on the server before rendering. To support this, new files were added for handling server-side revalidation, error states, loading skeletons, and the main server page logic, ensuring data is fetched on the server rather than the client.
apps/web/app/(use-page-wrapper)/event-types · high confidence
Server-side rendering for private booking links
Private booking links (e.g., /d/\[link\]/\[slug\]) now use a dedicated getServerSideProps implementation to fetch event data, user details, and branding settings on the server. This ensures that the page correctly handles redirects for non-organization links, validates hashed links early to return 404s for expired or invalid links, and determines whether to hide branding based on the associated user or team event before the page loads.
apps/web/lib/d · high confidence
Server-side setup page now enforces admin access and initializes license configuration
The /auth/setup page now requires an admin role to access, returning a 404 for non-admin users. Additionally, the server-side logic automatically persists the CALCOM\_LICENSE\_KEY environment variable into the deployment record if a license key is not already present, ensuring the initial setup state reflects the environment configuration.
apps/web/server/lib/setup · high confidence
Server-side validation and redirection for reschedule prevention
The reschedule page now enforces event-type settings (such as disabling rescheduling, blocking past bookings, or restricting cancelled bookings) via a server-side redirect before the UI loads. It also handles seated bookings by requiring a seat reference UID and verifying host/owner permissions, redirecting unauthenticated users to login if necessary.
apps/web/lib/reschedule · high confidence
Server-side validation for password reset requests
The forgot-password flow now includes a server-side props handler that validates password reset requests before rendering the page. It checks if the reset token is valid and not expired, and verifies that the associated user account still exists. If the request is invalid or the user no longer exists, the page will indicate that the request has expired, improving security by preventing unnecessary processing of invalid or stale reset tokens.
apps/web/server/lib/auth/forgot-password · high confidence
Sign-in page migrated to Next.js App Router
The sign-in page has been rewritten to use the Next.js App Router, replacing the previous implementation with a new server component that handles session checks and data fetching. This change introduces \withAppDirSsr\ to bridge legacy server-side logic with the new routing structure and utilizes Next 15 APIs like \next/headers\ and \next/navigation\ for context building and redirects, ensuring the authentication flow remains functional while adopting the modern framework architecture.
apps/web/app/(use-page-wrapper)/auth/signin · high confidence
Support for domain-wide delegation in destination calendar updates
The destination calendar service now supports updating calendars associated with domain-wide delegation credentials. The \updateDestinationCalendars\ method accepts an optional \delegationCredentialId\ parameter, allowing the system to locate and update specific delegated calendars rather than relying solely on standard user credentials. This change enables users to manage calendar destinations that are accessed via delegated service accounts.
apps/api/v2/src/modules/destination-calendars/services · high confidence
Timezone selection components moved to web modules
The TimezoneSelect, settings, and insights components have been relocated from the shared packages/features directory to the apps/web/modules/timezone directory. This structural change organizes the timezone UI logic within the web application's module system, while the underlying component implementation and test coverage remain intact to ensure consistent user experience in selecting and managing timezones.
apps/web/modules/timezone, packages/features/timezone · high confidence
Updated booker layout preview assets and default avatar
The static preview images for the column and month booker layouts have been replaced with new SVGs that reflect the updated Cal.com design, including specific dark-mode variants for the month view. Additionally, a new default avatar SVG has been added to replace the previous placeholder, ensuring consistent branding across the application.
apps/web/public · high confidence
Upgrade page refactored to use a server component wrapper
The upgrade page now renders the legacy UI view inside a dedicated async server component. This structural change ensures the page adheres to React Server Components best practices by avoiding the direct export of client components, while maintaining the existing metadata generation and user experience.
apps/web/app/(use-page-wrapper)/upgrade · high confidence
Version API route migrated to App Directory with error handling
The /api/version endpoint has been moved to the Next.js App Directory structure (apps/web/app/api/version/route.ts). This change replaces the previous implementation with a new route handler that uses the shared defaultResponderForAppDir wrapper, ensuring consistent error handling and reporting for this API endpoint.
apps/web/app/api/version · high confidence
Webhook creation and update inputs now support versioning and array-based triggers
The API v2 webhook input definitions have been updated to allow specifying a webhook version via the new optional \version\ field (using \WebhookVersion\ enum) and to require \triggers\ as an array of \WebhookTriggerEvents\ rather than a single string. These changes are reflected in the \CreateWebhookInputDto\ and \UpdateWebhookInputDto\ classes, which now include proper Swagger documentation for the new fields and validate the trigger list as an array of enums.
apps/api/v2/src/modules/webhooks/inputs · high confidence
Webhooks settings page now loads data server-side
The Webhooks settings page has been migrated to use Next.js Server Components, fetching webhook data directly on the server via the tRPC router before rendering the view. This change improves initial load performance and ensures the list is available without client-side data fetching, while also introducing a dedicated loading state component to display a skeleton UI while the server-side data is retrieved.
apps/web/app/(use-page-wrapper)/settings/(settings-layout)/developer/webhooks/(with-loader) · high confidence
tRPC API routes are split into dedicated endpoints
The tRPC API layer has been restructured so that each router (such as admin, apiKeys, apps, auth, availability, bookings, calendars, credentials, eventTypes, features, feedback, holidays, i18n, logged-in viewer, me, OAuth, OOO, public, slots, timezones, travel schedules, users, and webhooks) now has its own dedicated Next.js API page under apps/web/pages/api/trpc. This change means that tRPC calls are routed through specific endpoints rather than a single merged handler, which can improve performance and maintainability for both the client and server.
apps/web/pages/api/trpc · high confidence
Fixes
Corrected assignment reason badge mapping
The logic for determining the text displayed on booking assignment badges has been corrected. A new mapping function ensures that specific assignment reasons, such as reassignments, reroutes, and Salesforce assignments, are accurately reflected in the user interface instead of defaulting to generic labels.
apps/web/lib/booking · high confidence
Fix phone number truncation for Argentina, Finland, and other countries
The phone input component now includes custom masks for Argentina, Finland, Ivory Coast, Benin, and Austria to prevent valid phone numbers from being truncated. This ensures users can enter the full length of national digits for these regions, addressing issues where the library's default masks were outdated. Additionally, the component provides a stable country fallback logic to maintain correct formatting during async updates.
apps/web/components/phone-input · high confidence
Input validation for setup wizard step parameter
The /auth/setup page now validates the 'step' query parameter against a strict schema (values 1, 2, 3, or 4). If the parameter is missing or invalid, the user is automatically redirected to step 1, preventing potential crashes or undefined behavior in the setup wizard flow.
apps/web/app/(use-page-wrapper)/auth/setup · high confidence
Prevent disabled apps from appearing in app store category pages
The app store category pages now correctly filter out disabled applications. The new \getStaticProps\ implementation for category-specific pages queries the database for apps that are both present in the specified category and marked as \enabled: true\, ensuring that only active apps are displayed to users. This change addresses a bug where disabled apps were previously visible in these listings.
apps/web/lib/apps/categories · high confidence
Test coverage
2 commits adding/updating tests in specs; Added Checkly monitoring for dashboard, location links, and login CSP; Added E2E tests for Analytics Apps installation flows; Added E2E tests for Event Type availability and limits tabs; Added E2E tests for OAuth client approval workflow and authorization status; Added E2E tests for account deletion and password reset flows; Added E2E tests for the v2 Slots API (2024-09-04); Added e2e test for user avatar upload and display; Added e2e tests for Around Video conferencing app; Added integration tests for the selected-calendars cron job; Added mock assets for SVG hashes and Tailwind CSS; Added test coverage for signup handler error and invite flows; Added test infrastructure and configuration for the web app; Added tests for OAuth token exchange endpoint; Added tests for cancellation fee warnings in booking cancellation flow; Added tests for signup form validation behavior; Added tests for social OG image API validation and caching; Added tests for the EditLocationDialog component; Added tests for the recorded daily video webhook handler; Added tests for the request-reschedule booking handler; Added tests for theme provider logic in app, booking, and embed contexts; Added unit tests for availability, scheduling, and booking limit logic; Added unit tests for the getAvailableSlotsService; Expanded E2E test coverage for core booking and availability workflows; New Playwright E2E test fixtures for apps, bookings, and organizations; New Playwright test infrastructure and utilities; New testing utilities and performance benchmarks for Cal.diy; New unit tests for Cal.com and self-hosted signup handlers.
Dependencies
1991 commits updating dependencies (121 manifests)
A dependency / build maintenance change in (dependencies) — 1991 commits (310 fixs), 121 files: “Added -Add guest- button at confirm booking step, and minor code improvement”; “dependencies: update prisma to version 2.21.2”; “fix: channels removed”; and 1895 more (refs \#15457, \#2926, \#17586, \#18174, \#22321, …).
(dependencies) · high confidence · unverified
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 32 → 30 (-1.9)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.
Lenses
- Code Health 45 → 42 (-3.6)
- Architecture 41 → 41 (+0.1)
- Maturity 71 → 70 (-0.8)
- Readiness 22 → 18 (-4.2)
- Security 40 → 43 (+2.2)
- Domain Modelling 100 → 60 (-40.0)
- Accessibility 33 → 34 (+1.2)
- Performance 60 → 60 (+0.0)
Resolved (239)
- Critical CVE: [GHSA redacted] (yarn.lock)
- Critical CVE: [GHSA redacted] (apps/web/package.json)
- Critical CVE: [GHSA redacted] (apps/web/package.json)
- Critical CVE: [GHSA redacted] (packages/features/package.json)
- Critical CVE: [GHSA redacted] (yarn.lock)
- Critical CVE: [GHSA redacted] (apps/web/package.json)
- Critical CVE: [GHSA redacted] (yarn.lock)
- Critical CVE: [GHSA redacted] (yarn.lock)
- Critical vulnerability: [GHSA redacted] (apps/web/package.json)
- Critical vulnerability: [GHSA redacted] (example-apps/credential-sync/package.json)
- Cross-context type Action (atoms → ui) (packages/ui/components/card/FormCard.tsx)
- Cross-context type BlocklistScope (features → web) (apps/web/modules/blocklist/components/BlockedEntriesTable.tsx)
- Cross-context type BlocklistScope (features → web) (apps/web/modules/blocklist/components/BlocklistEntryDetailsSheet.tsx)
- Cross-context type BlocklistScope (features → web) (apps/web/modules/blocklist/components/BookingReportDetailsModal.tsx)
- Cross-context type BlocklistScope (features → web) (apps/web/modules/blocklist/components/CreateBlocklistEntryModal.tsx)
- Cross-context type BlocklistScope (features → web) (apps/web/modules/blocklist/components/PendingReportsTable.tsx)
- Cross-context type BookerLayoutsInputEnum_2024_06_14 (enums → types) (packages/platform/types/event-types/event-types_2024_06_14/inputs/booker-layouts.input.ts)
- Cross-context type BookerLayoutsInputEnum_2024_06_14 (enums → types) (packages/platform/types/event-types/event-types_2024_06_14/inputs/booker-layouts.input.ts)
- Cross-context type BookerLayoutsInputEnum_2024_06_14 (enums → types) (packages/platform/types/event-types/event-types_2024_06_14/inputs/booker-layouts.input.ts)
- Cross-context type BookingInputLocation_2024_08_13 (types → v2) (apps/api/v2/src/platform/bookings/2024-08-13/services/input.service.ts)
- …and 219 more
New (312)
- Deprecated: axios-retry (yarn.lock)
- Deprecated: axios-retry (yarn.lock)
- Deprecated: http-call (yarn.lock)
- Deprecated: next-axiom (apps/web/package.json)
- Deprecated: node-abort-controller (yarn.lock)
- Documentation: no build, run or usage example (packages/app-store-cli/README.md)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (packages/features/auth/package.json)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (packages/embeds/embed-react/package.json)
- High CVE: [GHSA redacted] (packages/embeds/embed-snippet/package.json)
- High CVE: [GHSA redacted] (packages/platform/atoms/package.json)
- High CVE: [GHSA redacted] (packages/platform/libraries/package.json)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (example-apps/credential-sync/package.json)
- …and 292 more
Changes since last survey
- 15 commits — 8 feature/other, 7 fixes
By area
- (root) — 4 commits
- packages/features — 3 commits
- packages/i18n — 3 commits
- .github/ISSUE_TEMPLATE — 1 commit
- .github/workflows — 1 commit
- packages/app-store — 1 commit
- packages/lib — 1 commit
- packages/platform — 1 commit
Notable commits
- fix: fix(bookings): send notification emails when calendar integrations fail (#30434)
- fix: fix(ci): restore release parsing and resolve critical audit failures (#30198)
- fix: fix(event-types): insert names and booking answers literally in custom event names (#30546)
- fix: fix(lib): add America/Coyhaique to the supported timezone list (#30448)
- fix: fix(security): bind redis and prisma studio ports to loopback in docker compose (#30359)
- fix: fix: remove dead Discussions links from issue template and constants (#30385)
- fix: fix: remove duplicated words in error messages and docs (#30409)
- change: chore(atoms): stop publishing @calcom/atoms from cal.diy (#30445)
- change: chore(i18n): remove remaining unused SMS workflow strings (#30470)
- change: chore(i18n): remove unused SMS workflow action strings (#30457)
- change: chore(i18n): remove unused WhatsApp workflow strings (#30446) (#30447)
- change: chore: remove Twilio page and unused Twilio env vars (#30442)
- change: chore: remove unused support chat env vars from .env.example (#30478)
- change: chore: upgrade Node.js from 20 to 22 (#30416)
- change: fix(bookings): trim whitespace in BLACKLISTED_GUEST_EMAILS (#30461)
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
calcom/cal.diy was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 14 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit ae027bb70e694e2d2c44569f398d6cbcee0389b1 — the exact code this score is about.
- Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.65+preprod-e1a3b69fc8ee.