Skip to content

fix(auth): restrict non-secure cookie fallback to development environment #5575

fix(auth): restrict non-secure cookie fallback to development environment

fix(auth): restrict non-secure cookie fallback to development environment #5575

Triggered via pull request July 8, 2026 16:49
Status Success
Total duration 1m 57s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 6 warnings
test/anthropic-service.test.ts > generateWeeklySummary — src/lib/anthropic.ts > returns null when the text block contains only whitespace: src/lib/anthropic.ts#L66
TypeError: () => ({ messages: { create: messagesCreate } }) is not a constructor ❯ getClient src/lib/anthropic.ts:66:15 ❯ generateWeeklySummary src/lib/anthropic.ts:134:18 ❯ test/anthropic-service.test.ts:232:26
test/anthropic-service.test.ts > generateWeeklySummary — src/lib/anthropic.ts > returns null when the API response has no text block: src/lib/anthropic.ts#L66
TypeError: () => ({ messages: { create: messagesCreate } }) is not a constructor ❯ getClient src/lib/anthropic.ts:66:15 ❯ generateWeeklySummary src/lib/anthropic.ts:134:18 ❯ test/anthropic-service.test.ts:219:26
test/anthropic-service.test.ts > generateWeeklySummary — src/lib/anthropic.ts > uses 'none' for topRepo when the value is null: src/lib/anthropic.ts#L66
TypeError: () => ({ messages: { create: messagesCreate } }) is not a constructor ❯ getClient src/lib/anthropic.ts:66:15 ❯ generateWeeklySummary src/lib/anthropic.ts:134:18 ❯ test/anthropic-service.test.ts:202:11
test/anthropic-service.test.ts > generateWeeklySummary — src/lib/anthropic.ts > preserves special characters in topRepo (no HTML encoding): src/lib/anthropic.ts#L66
TypeError: () => ({ messages: { create: messagesCreate } }) is not a constructor ❯ getClient src/lib/anthropic.ts:66:15 ❯ generateWeeklySummary src/lib/anthropic.ts:134:18 ❯ test/anthropic-service.test.ts:188:11
test/anthropic-service.test.ts > generateWeeklySummary — src/lib/anthropic.ts > includes all key metrics in the JSON payload: src/lib/anthropic.ts#L66
TypeError: () => ({ messages: { create: messagesCreate } }) is not a constructor ❯ getClient src/lib/anthropic.ts:66:15 ❯ generateWeeklySummary src/lib/anthropic.ts:134:18 ❯ test/anthropic-service.test.ts:167:11
test/anthropic-service.test.ts > generateWeeklySummary — src/lib/anthropic.ts > encodes metrics as structured JSON — user message is valid JSON: src/lib/anthropic.ts#L66
TypeError: () => ({ messages: { create: messagesCreate } }) is not a constructor ❯ getClient src/lib/anthropic.ts:66:15 ❯ generateWeeklySummary src/lib/anthropic.ts:134:18 ❯ test/anthropic-service.test.ts:153:11
test/anthropic-service.test.ts > generateWeeklySummary — src/lib/anthropic.ts > sends max_tokens ≤ 200 (enough for 2–3 sentences, not an essay): src/lib/anthropic.ts#L66
TypeError: () => ({ messages: { create: messagesCreate } }) is not a constructor ❯ getClient src/lib/anthropic.ts:66:15 ❯ generateWeeklySummary src/lib/anthropic.ts:134:18 ❯ test/anthropic-service.test.ts:137:11
test/anthropic-service.test.ts > generateWeeklySummary — src/lib/anthropic.ts > calls the SDK with the correct model: src/lib/anthropic.ts#L66
TypeError: () => ({ messages: { create: messagesCreate } }) is not a constructor ❯ getClient src/lib/anthropic.ts:66:15 ❯ generateWeeklySummary src/lib/anthropic.ts:134:18 ❯ test/anthropic-service.test.ts:124:11
test/anthropic-service.test.ts > generateWeeklySummary — src/lib/anthropic.ts > returns the trimmed summary string on a successful API call: src/lib/anthropic.ts#L66
TypeError: () => ({ messages: { create: messagesCreate } }) is not a constructor ❯ getClient src/lib/anthropic.ts:66:15 ❯ generateWeeklySummary src/lib/anthropic.ts:134:18 ❯ test/anthropic-service.test.ts:112:26
test/GoalTracker.test.ts > GoalTracker - useGoalTracker Hook > handles sync failures gracefully: test/GoalTracker.test.ts#L146
AssertionError: expected 'Sync failed. Please try again.' to be 'Failed to sync goals. Please try agai…' // Object.is equality Expected: "Failed to sync goals. Please try again." Received: "Sync failed. Please try again." ❯ test/GoalTracker.test.ts:146:38
Lint: src/components/SponsorAnalytics.tsx#L364
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
Lint: src/components/ProfileCard.tsx#L38
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
Lint: src/app/settings/page.tsx#L69
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
Lint: src/app/dashboard/settings/page.tsx#L1700
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
Lint: src/app/api/og/user/route.tsx#L36
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
Coverage report unavailable
Vitest did not produce a coverage summary. This warning does not fail CI.