docs: Add November 2025 Changelog

[tembo]

Summary

This PR adds a comprehensive changelog for the November 2025 release period (October 22 - November 18, 2025).

What's Included

The changelog documents all major changes from the past month, organized by date and categorized for clarity:

Key Highlights

• SDK Improvements: OpenAI SDK middleware support (TypeScript & Python)
• Major Upgrades: Next.js 16, IndexedDB migration, WXT Storage API
• Security Fixes: Message recipient verification vulnerability
• UX Enhancements: Better loading states, inline confirmations, mobile responsiveness
• Bug Fixes: Multiple Sentry-reported errors, hydration issues, organization switching
• Documentation: Enhanced API docs, self-hosting guide, personal assistant cookbook

Format

The changelog follows the existing format used in apps/docs/changelog/developer-platform.mdx, with:

• Clear date-based organization
• Descriptive titles and PR references
• User-focused language
• Links to relevant pull requests

Testing

• Changelog file is properly formatted as MDX
• All PR links are valid
• Dates are accurate
• Content is clear and user-friendly

---

Generated by: Automated workflow from Tembo
Related: This changelog was also prepared to be shared in the #engineering Slack channel

[graphite-app]

How to use the Graphite Merge Queue

Add the label Main to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[claude]

Pull Request Review

Thank you for this comprehensive changelog! Overall, this is a well-structured and informative document.

Strengths

Code Quality & Structure

• Excellent formatting: The MDX structure follows the existing pattern consistently
• Clear organization: Chronological ordering (newest first) makes it easy to find recent changes
• Good metadata: Proper frontmatter with title and description
• Comprehensive coverage: 116 additions covering a full month of development activity

Content Quality

• User-focused language: Changes are described in terms of user benefit
• Proper attribution: All entries include PR references with links for traceability
• Contextual information: Each change includes the why along with the what
• Professional tone: Consistent, clear writing throughout

Issues & Recommendations

1. Temporal Anomaly - CRITICAL

The changelog is dated November 2025 but covers dates from October 22 - November 18, 2025. According to the environment context, today is 2025-11-19.

Recommendations:

• If this is meant to be for work completed in the past (2024), all dates should be corrected to 2024
• If covering two months, consider renaming to October-November 2025 Release or splitting into two separate changelogs
• The filename november-2025.mdx should match the actual time period covered

2. Documentation Integration

The new changelog file is not linked anywhere in the documentation navigation.

Missing steps:

• Update apps/docs/changelog/overview.mdx to include a card for this November 2025 release
• The overview page currently shows September 2025 as What's New This Month but should be updated for November
• Consider updating the mint.json navigation config if changelogs are listed there

3. Security Considerations

For the message verification vulnerability (PR #565), consider adding:

• Affected versions
• Whether this affects the Chrome extension, web app, or both
• Recommended action for users (e.g., Users should update to the latest extension version)

The IndexedDB migration (PR #560) involves client-side data storage changes - verify there is a migration path for existing localStorage data.

4. Content Accuracy

Items to verify:

• Security fix (Nov 7): Consider adding a CVE identifier if applicable and severity level
• Temporarily disabled features (Nov 4): Google Drive is marked as temporarily disabled - is this still accurate as of the PR date?
• October dates: About 1/3 of the changelog covers October. Consider renaming to reflect the full date range.

Test Coverage

The PR description includes a testing checklist but it is incomplete. Recommendations:

1. Add a CI check or script to validate all PR links return 200 status, MDX syntax is valid, and dates are in chronological order
2. Verify the changelog renders correctly in the docs site (consider adding a screenshot)
3. Test that internal links work correctly

Action Items

Before Merging:

1. Fix date references - Clarify if this is 2024 or 2025, adjust all dates accordingly
2. Update navigation - Add this changelog to overview.mdx and any relevant navigation configs
3. Verify PR links - Ensure all 40+ PR references are valid and accessible
4. Complete security details - Add actionable information for the security vulnerability fix
5. Check Google Drive status - Verify if it is still disabled or update the entry
6. Complete testing checklist - Mark items as done or remove the checklist

Summary

This is a high-quality changelog that demonstrates excellent documentation practices. The main issues are:

1. Date/timeline inconsistencies that need clarification
2. Missing integration with the documentation navigation
3. Minor opportunities for enhanced structure and security detail

Once the date issues are resolved and navigation is updated, this is ready to merge.

Estimated effort to address issues: ~30 minutes

Great work on documenting this release!

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	supermemory-app	e229909	Nov 19 2025, 08:10 AM

[claude]

Code Review - November 2025 Changelog

✅ Overall Assessment

This is a well-structured and comprehensive changelog that effectively documents a month of significant development. The content is clear, well-organized, and follows good documentation practices.

---

📋 Code Quality & Structure

Strengths:

• Excellent organization: Chronological ordering with clear date headers makes it easy to track changes over time
• Consistent formatting: Follows the established pattern from developer-platform.mdx
• Good MDX structure: Proper frontmatter with title and description
• Clear categorization: Changes are well-described with appropriate emphasis on major features
• Proper attribution: Includes PR links and contributor acknowledgments

Minor Issues:

1. Date accuracy concern: Some dates may reflect merge dates rather than release dates. For example:

   • PR Fix: Prevent multiple prompts while AI response is generated (fixes #538) #583 merged on Nov 18, but appears under Nov 18 ✓
   • PR Fix: Messages Sent to Any Website Without Verifying Recipient in apps/web/app/(navigation)/page.tsx #565 merged on Nov 7, appears under Nov 7 ✓
   • PR Migrate Chat Persistence from localStorage to IndexedDB to Fix QuotaExceededError #560 merged on Nov 7, but appears under Nov 7 ✓

   Dates appear correct based on merge dates.

---

🔍 Content Review

Strengths:

• User-focused language: Descriptions explain the "why" and impact, not just the "what"
• Comprehensive coverage: Includes SDK improvements, security fixes, UX enhancements, bug fixes, and documentation
• Security transparency: Properly highlights the critical security fix (PR Fix: Messages Sent to Any Website Without Verifying Recipient in apps/web/app/(navigation)/page.tsx #565) without being alarmist
• Good context: Each entry provides sufficient detail for users to understand the change

Suggestions:

1. Package updates section: Consider being more specific about what "streaming support and enhanced memory handling" means in version 1.3.1
2. Contributors section: The list is comprehensive but consider highlighting first-time contributors if applicable

---

🐛 Potential Issues

None Found - No bugs or code issues detected in this documentation change.

---

⚡ Performance Considerations

N/A - This is a documentation file with no performance impact.

---

🔒 Security Review

Strengths:

• Proper disclosure: Security vulnerability (PR Fix: Messages Sent to Any Website Without Verifying Recipient in apps/web/app/(navigation)/page.tsx #565) is documented appropriately without exposing exploit details
• No sensitive data: No API keys, tokens, or sensitive information exposed

---

🧪 Test Coverage

Documentation Navigation:

• ✅ File location: apps/docs/changelog/november-2025.mdx follows the pattern
• ⚠️ Navigation config update needed: The file is not yet referenced in docs.json line 254

Action Required:
The docs.json navigation configuration needs to be updated to include this new changelog:

"pages": ["changelog/overview", "changelog/developer-platform", "changelog/november-2025"]

Currently at line 254, it only includes:

"pages": ["changelog/overview", "changelog/developer-platform"]

---

📝 Recommendations

1. Update docs.json (Required):

   • Add "changelog/november-2025" to the changelog pages array in docs.json at line 254

2. Update overview.mdx (Recommended):

   • Update changelog/overview.mdx to reflect November 2025 as the latest month instead of September 2025
   • Update the "Latest" section in the CardGroup

3. Consistency check (Nice to have):

   • Consider whether this should be titled "November 2025 Release" or "November 2025" to match the other changelog (which is titled "Developer Platform" not "Developer Platform Release")

4. Add second CardGroup (Consider):

   • The overview.mdx currently only has one card for "Developer Platform". Consider adding a second card for "Product Updates" or similar to house this new changelog category.

---

🎯 Summary

Approval Status: ✅ Approve with minor changes required

Required Changes:

• Update apps/docs/docs.json to add the new changelog to navigation

Recommended Changes:

• Update apps/docs/changelog/overview.mdx to reflect November as the latest month

What's Excellent:

• Comprehensive coverage of changes
• Clear, user-friendly language
• Proper PR attribution
• Good security disclosure practices
• Follows established formatting patterns

This is high-quality documentation work that will help users understand the significant progress made in November 2025!

---

Review generated by Claude Code