feat(calendar): unified calendar view with meetings, milestones, and sprints #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

dimakis merged 4 commits into main from feat/calendar-view

Apr 10, 2026

Merged

feat(calendar): unified calendar view with meetings, milestones, and sprints #164

style: format global.css with prettier

Annotations

2 errors and 11 warnings

Test: server/__tests__/hook-bridge.test.ts#L207

Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ server/__tests__/hook-bridge.test.ts:207:3

Test: server/hook-bridge.ts#L155

Error: write EPIPE ❯ server/hook-bridge.ts:155:21 ❯ server/hook-bridge.ts:121:12 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -32, code: 'EPIPE', syscall: 'write' } This error originated in "server/__tests__/hook-bridge.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "returns parsed JSON from a successful command". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Complete job

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/

Lint: server/__tests__/permissions.test.ts#L74