Configure Stripe production deployment#287
Merged
Merged
Conversation
…d better form handling
- Create /insights/launch-announcement page with full press release - Add launch announcement card to Insights index - Update About page news section with press release link - Add route for /insights/launch-announcement in http.ts
The pricing table was being rendered in HTML without the customer-session-client-secret attribute. By the time JavaScript fetched the session and tried to setAttribute(), the Stripe web component had already initialized and ignored the change. Fix: Dynamically create the pricing table element after loading the customer session, ensuring all attributes are set before the component initializes. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Personal workspaces now show STRIPE_PRICING_TABLE_ID_INDIVIDUAL while team workspaces show STRIPE_PRICING_TABLE_ID. Falls back to the main pricing table ID if the individual one isn't configured. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- Add join request database with pending/approved/rejected states - Add email domain utility for matching users to organizations - Add free-email-domains package to detect personal email providers - Update onboarding UI to show joinable organizations based on email domain - Add migration for organization_join_requests table 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
3 tasks
bokelley
added a commit
that referenced
this pull request
Apr 28, 2026
…itative (#3380) Found via escalation #287 (wheelrandom.com). Publisher's adagents.json was valid and anchored, but registry showed 0 authorizations. Root cause: when projectPropertyToCatalog adopts a foreign rid via the publisher-anchor path (Rule 4), the UPDATE refreshed adagents_url + property_id only — leaving source='contributed' and created_by='community:foo' (or whatever pipeline previously owned the rid). The auth projection's `WHERE created_by = 'adagents_json:<pub>' AND property_id = ANY(...)` then returned zero rows, and authorized_agents[] entries silently dropped. Fix: also set source='authoritative' and created_by=expectedCreatedBy on the adopt path. The publisher with a matching anchor is now the source-of-truth pipeline for this property; its created_by should reflect that. Idempotent for own re-crawls (the SET is a no-op when matchedCreatedBy already equals expectedCreatedBy). Test added (registry-catalog-agent-auth-writer.test.ts): pre-seed a 'contributed'/'community:<pub>' catalog row + identifier, then crawl an adagents.json that references the same domain. Asserts the rid is reused, source promoted to 'authoritative', created_by rebound, and the auth projection lands a CAA row referencing the promoted rid. Refs #3177.
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.
Summary
Configures Stripe production secrets (publishable key, secret key, pricing table ID, and webhook signing secret) for live billing integration.
All Stripe secrets have been set in the Fly.io production environment and are ready for live payment processing.
Changes
customer.subscription.created,customer.subscription.updated,customer.subscription.deleted) enabled