v0.5.103: memory util instrumentation, API docs, amplitude, google pagespeed insights, pagerduty

[waleedlatif1]

• fix(monitoring): set MemoryTelemetry logger to INFO level for production visibility (fix(monitoring): set MemoryTelemetry logger to INFO for production #3386)
• feat(integrations): add amplitude, google pagespeed insights, and pagerduty integrations (feat(integrations): add amplitude, google pagespeed insights, and pagerduty integrations #3385)
• feat(docs): add API reference with OpenAPI spec and auto-generated endpoint pages (feat(docs): add API reference with OpenAPI spec and auto-generated endpoint pages #3388)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Building	Preview, Comment	Mar 2, 2026 6:54am

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is kicking off a free cloud agent to fix these issues. This run is complimentary, but you can enable autofix for all future PRs in the Cursor dashboard.}

[cursor]

Navbar links lose language context for non-English users

Medium Severity

The new "Documentation" and "API" nav links use hardcoded English paths (/introduction and /api-reference/getting-started) without including the current language prefix. Since hideLocale is set to 'default-locale', these paths always resolve to English. Non-English users (e.g. browsing at /de/...) who click either link silently lose their language context. The component already calls usePathname() and could extract the language prefix, similar to how stripLangPrefix works in the sidebar components.

 

[greptile-apps]

Greptile Summary

This release (v0.5.103) adds three major features:

Memory Telemetry Enhancement

• Set MemoryTelemetry logger to INFO level for better production visibility - simple one-line change that ensures memory metrics are captured in production logs

New Integrations

• Amplitude: Comprehensive analytics integration with 11 operations (event tracking, user identification, segmentation, revenue analytics)
• Google PageSpeed Insights: Web performance analysis tool with Lighthouse metrics
• PagerDuty: Incident management integration with 6 operations (list/create/update incidents, on-call schedules)

All three integrations follow established patterns with proper block configurations, tool implementations, and registry entries. API keys use user-only visibility as expected.

API Documentation System

• Added OpenAPI specification (1,893 lines) defining all API endpoints
• Created openapi.ts utilities for spec parsing and reference resolution
• Enhanced docs page routing to render API reference pages with fumadocs-openapi
• Built custom ResponseSection component for interactive API response display
• Added 679 lines to global.css for OpenAPI styling (consider component-scoped alternatives per project guidelines)

The documentation includes auto-generated pages for all languages (en, es, fr, de, ja, zh) with proper authentication guides and SDK examples.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• All changes follow established patterns and conventions. The memory telemetry change is trivial, the three new integrations are well-structured with proper error handling and type safety, and the API documentation system is a comprehensive addition that doesn't modify existing functionality. The only consideration is the large global.css addition, which is addressed with a style suggestion.
• No files require special attention - all implementations are clean and follow project standards

Important Files Changed

Filename	Overview
apps/sim/blocks/blocks/amplitude.ts	New Amplitude integration block with comprehensive operation support - well-structured configuration following established patterns
apps/sim/blocks/blocks/google_pagespeed.ts	New Google PageSpeed Insights integration block - clean configuration with appropriate fields
apps/sim/blocks/blocks/pagerduty.ts	New PagerDuty integration block with incident management operations - properly structured with conditional fields
apps/docs/lib/openapi.ts	New OpenAPI spec processing utilities with reference resolution and formatting - solid implementation with depth limiting
apps/docs/app/[lang]/[[...slug]]/page.tsx	Enhanced docs page with OpenAPI support - proper conditional rendering for API reference pages
apps/docs/components/ui/response-section.tsx	Custom response section component for API docs using MutationObserver - well-implemented with proper cleanup
apps/docs/app/global.css	Added 679 lines of OpenAPI-specific styling - extensive changes that might benefit from component-scoped styles where possible
apps/sim/blocks/registry.ts	Registered three new blocks (Amplitude, Google PageSpeed, PagerDuty) - straightforward additions
apps/sim/tools/registry.ts	Registered 19 new tools across the three integrations - complete and properly organized

_{Last reviewed commit: 79bb4e5}

[greptile-apps]

_{91 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

679 lines added to global.css for OpenAPI styling. Per project guidelines, consider if some styles could be moved to component-scoped CSS modules or styled-components to reduce global scope.

Context Used: Rule from dashboard - Avoid editing the globals.css file unless absolutely necessary. Move style changes to local componen... (source)