chore(release): staging to production - 2025.11.12 - #683
Merged
Conversation
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Implements Linear MCP server integration with the following components: - Linear API credential (LinearApi.credential.ts) for secure API key storage - Linear MCP node (LinearMCP.ts) using SSE transport to connect to https://mcp.linear.app/sse - Linear icon (linear.svg) for UI display - Dynamic action loading via asyncMultiOptions - Comprehensive error handling for invalid credentials Follows TheAnswer MCP node patterns with tags: ['AAI'] and category: 'MCP Servers'. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…r-mcp-node-to-theanswer feat(AGENT-132): add Linear MCP node integration
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…vas-back-button fix(AGENT-133): fix back button navigation for agent canvas
Add validation and error handling for invalid Stripe customer IDs in usage sync: - Add customer ID validation before Stripe API calls (StripeProvider.ts:398-414) - Handle "Customer not found" errors with automatic fallback to default customer (StripeProvider.ts:463-486, 509-513) - Validate BILLING_DEFAULT_STRIPE_CUSTOMER_ID at server startup (config.ts:12-18) - Fix null safety by removing unsafe non-null assertions (LangfuseProvider.ts:589) - Document BILLING_DEFAULT_STRIPE_CUSTOMER_ID as required in .env.template This prevents the billing sync cron job from failing when encountering invalid customer IDs from Langfuse trace metadata. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…errors Use .includes() instead of exact match to handle variations in Stripe error parameter format: - Handles 'payload[stripe_customer_id]', 'stripe_customer_id', etc. - Adds optional chaining (?.) for null safety - More robust against future Stripe API changes 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…izationId for multi-tenancy - Add safeguard in _saveChunksToStorage to set userId/organizationId from entity - Create migration to backfill existing chunks with NULL values - Prevents privacy/multi-tenancy issues where users can't access their chunks 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Follow-up prompt traces were missing critical billing metadata fields, causing billing sync to fail. This adds all required fields to match the metadata structure of regular message traces. Changes: - Add billedUserId resolution (authenticated user OR chatflow owner) - Pass messageId, organizationId, trackingMetadata to follow-up prompts - Pass billingStripeCustomerId for correct billing attribution - Update followUpPrompts.ts metadata to match handler.ts structure - Add detailed comments explaining billing customer ID pattern Metadata now includes: ✅ messageId - Links to parent message ✅ organizationId - Multi-tenancy filtering ✅ trackingMetadata - Custom tracking fields ✅ stripeCustomerId/customerId - Billing attribution ✅ userId - Actual user context Files modified: - packages/server/src/utils/buildChatflow.ts (agent + regular flows) - packages/components/src/followUpPrompts.ts (metadata structure) Related: AGENT-153
…ging Updates handler.ts to use billingStripeCustomerId (from billedUserId pattern) for trace metadata, ensuring correct billing attribution when user is undefined (public/embedded chatflows bill the chatflow owner). Also removes verbose logging in StripeProvider.getUpcomingInvoice to reduce log noise. Changes: - handler.ts: Use billingStripeCustomerId with fallback to user.stripeCustomerId - handler.ts: Add comments explaining billedUserId pattern - StripeProvider.ts: Remove debug log.info statements Related: AGENT-153
The executeAgentFlow path was missing the same billing metadata fields that were added to buildChatflow.ts. Agent flows executed through this path had traces missing organizationId, customerId/stripeCustomerId, and tracking data, causing billing sync to fail. This updates the agentflow generateFollowUpPrompts call to match the pattern used in buildChatflow.ts: - Add billedUserId resolution (authenticated user OR chatflow owner) - Pass messageId, organizationId, trackingMetadata - Pass billingStripeCustomerId for correct billing attribution - Import User entity and billing config constants Now all three follow-up prompt call sites have identical metadata: 1. buildChatflow.ts agent flows (lines 679-700) 2. buildChatflow.ts regular flows (lines 895-916) 3. buildAgentflow.ts (lines 1898-1925) ✅ FIXED Related: AGENT-153
…762986183547 Add Claude Code GitHub Workflow
github-actions
Bot
changed the title
…ent-loader-chunk-count fix(AGENT-127): ensure document store chunks always have userId/organizationId for multi-tenancy
…ge-sync-handle-customer-not-found-errors fix(AGENT-64): handle Stripe customer not found errors gracefully
…ng-billing-metadata-in-follow-up-prompt-traces fix(AGENT-153): add complete billing metadata to follow-up prompt traces
maxtechera
temporarily deployed
to
staging - aai-unified2-flowise-moonstruck
November 12, 2025 22:33 — with 
Render
Inactive
Render
Inactive
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
2 participants
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.
🚀 Release: Staging to Production
Release Date: 2025-11-12
Changes in this release
This PR is automatically created/updated when commits are pushed to staging.
Merging this PR will trigger the release workflow to create a new GitHub release.