Skip to content

Conversation

@ptnghia-j
Copy link
Owner

@ptnghia-j ptnghia-j commented Dec 14, 2025

Fixed YouTube Info Endpoint (404 Issue)

File Modified: src/app/analyze/[videoId]/metadata.ts

Problem: The code was calling /api/youtube/info directly on the Python backend (Cloud Run), but that endpoint was intentionally removed in v0.5.3. The YouTube info endpoint now exists only as a Next.js API route.

Solution: Updated fetchVideoInfo() to call the internal Next.js API route instead:

Changed from: ${PYTHON_BACKEND_URL}/api/youtube/info (POST)
Changed to: ${NEXT_JS_URL}/api/youtube/info?videoId=xxx (GET)
Also mapped the response fields correctly (uploader → channelTitle, thumbnail → thumbnailUrl)

Security Patches Applied

Vulnerabilities Addressed:

CVE-2025-55184 (High Severity - Denial of Service)
CVE-2025-55183 (Medium Severity - Source Code Exposure)
CVE-2025-67779 (Complete DoS Fix)
Package Updated:

next: ^15.3.5 → ^15.3.8

Minor UI change in homepage

  1. Hero Section Subtitle Typography
    File Modified: src/components/homepage/NewHomePageContent.tsx

  2. App Logo Title Font
    Files Modified:

src/app/layout.tsx - Added Nunito font from Google Fonts
tailwind.config.js - Added font-nunito to the font family configuration
src/components/common/Navigation.tsx - Applied Nunito font to logo text
src/components/common/Footer.tsx - Applied Nunito font for consistency

  1. Recent Analyses Section Layout
    File Modified: src/components/homepage/RecentVideos.tsx

@augmentcode
Copy link

augmentcode bot commented Dec 14, 2025

This pull request is too large for Augment to review. The PR exceeds the maximum size limit of 100000 tokens (approximately 400000 characters) for automated code review. Please consider breaking this PR into smaller, more focused changes.

@ptnghia-j ptnghia-j merged commit d4a5491 into main Dec 14, 2025
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants