HOTFIX: Update packages embed - #628
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
maxtechera
temporarily deployed
to
staging - aai-unified2-flowise-moonstruck
October 23, 2025 16:44 — with 
Render
Inactive
Render
Inactive
maxtechera
added a commit
that referenced
this pull request
Oct 24, 2025
# Release: Staging to Production - October 24, 2025 This PR releases all tested changes from staging to production. ## 🎯 Key Features ### Organizational Billing Override (#637) - **NEW**: Support for organizational billing where all users' usage consolidates to a single Stripe customer - Environment variable: `BILLING_OVERRIDE_CUSTOMER_ID=true` to enable - Users maintain individual trace attribution while billing flows to organization - Fixes P1 issue where usage events returned empty list for organizational accounts ### Langfuse API Optimization (#637) - **PERFORMANCE**: Reduced parallel API load by 85% - PAGE_BATCH_SIZE: 15 → 3 pages - TRACE_BATCH_SIZE: 15 → 5 traces - RATE_LIMIT_DELAY_MS: 1000ms → 2000ms - LOOKBACK_DAYS: 90 → 7 days (default) - Prevents "database resource limit exceeded" errors on large datasets - All settings configurable via environment variables ### Environment Variable Standardization (#637) - **BREAKING**: All billing-related env vars now use `BILLING_` prefix - `STRIPE_FREE_PRICE_ID` → `BILLING_STRIPE_FREE_PRICE_ID` - `STRIPE_CREDITS_METER_ID` → `BILLING_STRIPE_CREDITS_METER_ID` - `STRIPE_AI_TOKENS_METER_ID` → `BILLING_STRIPE_AI_TOKENS_METER_ID` - `STRIPE_MARGIN_MULTIPLIER` → `BILLING_STRIPE_MARGIN_MULTIPLIER` - Updated documentation and code references ## 🐛 Bug Fixes ### P1: Usage Events Filter for Organizational Billing - Fixed filter logic in `getUsageEvents` to handle organizational override - Users now correctly see their own traces when override is enabled - Admins continue to see all traces ### Billing Metadata and Tracking - Previous releases included billing metadata filtering improvements - Self-healing for billing tags - Enhanced analytics tracing accuracy ## 📋 Other Improvements - Chat drawer pagination enhancements - Facebook Pixel tracking fixes - JLINC audit log improvements - Admin navigation fixes - Dependencies updates (mammoth 1.10.0 → 1.11.0) ## 🔄 Migration Notes **Required Environment Variable Updates:** Update your production environment with the new `BILLING_STRIPE_*` prefixed variables. The old names will no longer work. **New Optional Variables:** - `BILLING_OVERRIDE_CUSTOMER_ID` - Set to "true" for organizational billing - `BILLING_DEFAULT_STRIPE_CUSTOMER_ID` - Organization's Stripe customer ID - `BILLING_SYNC_LOOKBACK_DAYS` - Days to look back for unprocessed traces (default: 7) - `BILLING_SYNC_PAGE_BATCH_SIZE` - Parallel page fetches (default: 3) - `BILLING_SYNC_TRACE_BATCH_SIZE` - Parallel trace fetches (default: 5) - `BILLING_SYNC_RATE_LIMIT_MS` - Delay between API calls (default: 2000) ## ✅ Testing All changes have been tested in staging environment including: - Organizational billing override functionality - Langfuse API optimization under load - Usage events filtering with override enabled - Environment variable migrations ## 📦 Included PRs - #637 - Organizational billing override and Langfuse optimization - #635 - Previous staging release - #628 - Embed package updates - #627 - Previous production release - #622 - Billing metadata filtering - #621 - Chat drawer pagination - #617 - Billing tag self-healing - And more (see commit history) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.