Skip to content

fix: include title, location, duration in next/prev event api response #829

fix: include title, location, duration in next/prev event api response

fix: include title, location, duration in next/prev event api response #829

Triggered via pull request April 13, 2026 15:43
Status Success
Total duration 7m 50s
Artifacts

validate.yaml

on: pull_request
Matrix: Validate
Build and deploy  /  Detect changed apps
Build and deploy / Detect changed apps
Matrix: Build and deploy / Build and push docker images
Waiting for pending jobs
Build and deploy  /  Build and push docker images
Build and deploy / Build and push docker images
Matrix: Build and deploy / Deploy docker images
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

12 warnings and 2 notices
Validate (24.x, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Validate (24.x, ubuntu-24.04)
No files were found with the provided path: playwright-report/. No artifacts will be uploaded.
Validate (24.x, ubuntu-24.04): packages/ui/lib/menu.tsx#L214
Use destructuring assignment for component props
Validate (24.x, ubuntu-24.04): packages/ui/lib/date-picker.tsx#L59
A/an 'object expression' as default prop. This could lead to potential infinite render loop in React. Use a variable instead of 'object expression'
Validate (24.x, ubuntu-24.04): packages/ui/lib/command-menu.tsx#L107
A/an 'object expression' passed as the value prop to the context provider should not be constructed. It will change on every render. Consider wrapping it in a useMemo hook
Validate (24.x, ubuntu-24.04): packages/ui/lib/command-menu.tsx#L106
A/an 'object expression' passed as the value prop to the context provider should not be constructed. It will change on every render. Consider wrapping it in a useMemo hook
Validate (24.x, ubuntu-24.04): packages/ui/lib/carousel.tsx#L137
A/an 'object expression' passed as the value prop to the context provider should not be constructed. It will change on every render. Consider wrapping it in a useMemo hook
Validate (24.x, ubuntu-24.04): packages/ui/lib/carousel.tsx#L81
onSelect is only used inside 1 useEffect, which may be unnecessary. You can move the computation into useEffect directly and merge the dependency arrays
Validate (24.x, ubuntu-24.04): packages/ui/lib/calendar.tsx#L199
Do not use item index in the array as its key
Validate (24.x, ubuntu-24.04): packages/ui/lib/calendar.tsx#L159
Do not use item index in the array as its key
Validate (24.x, ubuntu-24.04): packages/ui/lib/breadcrumbs.tsx#L21
A context name must be a valid component name with the suffix 'Context'
Validate (24.x, ubuntu-24.04): packages/ui/lib/avatar.tsx#L79
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
🎭 Playwright Run Summary
30 skipped 99 passed (2.1m)
🎭 Playwright Run Summary
45 skipped 84 passed (1.3m)