v0.6.43: mothership billing idempotency, env var resolution fixes

[icecrasher321]

• fix(billing): add idempotency to billing (fix(billing): add idempotency to billing #4157)
• fix(triggers): env var resolution in provider configs (fix(triggers): env var resolution in provider configs #4160)
• fix(google-drive): add auto export format and validate against Drive API docs (fix(google-drive): add auto export format and validate against Drive API docs #4161)
• feat(jira): support raw ADF in description and environment fields (feat(jira): support raw ADF in description and environment fields #4164)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 14, 2026 10:18pm

[cursor]

PR Summary

Medium Risk
Touches billing usage recording to prevent double-charging and changes webhook execution input shaping via provider-config env var resolution; mistakes could block usage updates or break webhook triggers.

Overview
Adds optional idempotencyKey handling to POST /api/billing/update-cost, atomically claiming a billing-scoped key and returning 409 on duplicates; on failure it now releases the claim only if usage was not committed to avoid double-billing.

Fixes webhook trigger executions to resolve {{ENV_VAR}} references inside stored providerConfig before calling provider formatInput, with a small wrapper that rethrows errors with provider/webhook context. Adds focused Vitest coverage for the new env resolver and the webhook-execution wrapper.

^{Reviewed by Cursor Bugbot for commit 7529a75. Configure here.}

[greptile-apps]

Greptile Summary

This PR adds idempotency to the billing update-cost API route (atomic claim/release pattern with a 1-hour TTL) and fixes env var resolution in webhook provider configs by resolving {{VAR}} references before passing the webhook record to handler.formatInput. Both changes are paired with focused unit tests.

Confidence Score: 5/5

Safe to merge — all changes are correct, well-tested, and follow project conventions with no blocking issues.

Both features are implemented correctly. The billing idempotency uses the atomic claim/release pattern properly: pre-commit failures release the key so the caller can retry, post-commit failures retain it to prevent double-billing, and duplicates within the 1-hour TTL receive 409. The env-resolver functions are clean, type-safe, and covered by tests. No P0 or P1 findings.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/app/api/billing/update-cost/route.ts	Adds optional idempotency key support: atomically claims before processing, releases on pre-commit failure, and retains on post-commit failure to prevent double-billing. Logic is correct.
apps/sim/lib/core/idempotency/service.ts	Adds a public release() wrapper for the private deleteKey() method and exports a new billingIdempotency instance with a 1-hour TTL. Changes are minimal and correct.
apps/sim/lib/webhooks/env-resolver.ts	Adds normalizeWebhookProviderConfig, resolveWebhookProviderConfig, and resolveWebhookRecordProviderConfig to resolve env var references inside webhook provider configs. Clean generic design with proper null handling.
apps/sim/background/webhook-execution.ts	Exports resolveWebhookExecutionProviderConfig (wrapper with contextual errors) and calls it on the fetched webhook record before handing it to handler.formatInput, fixing env var resolution in provider configs.
apps/sim/lib/webhooks/env-resolver.test.ts	Well-structured tests covering deep env var resolution and record cloning. Correctly mocks getEffectiveDecryptedEnv via vi.hoisted pattern per project standards.
apps/sim/background/webhook-execution.test.ts	Tests success and failure paths of resolveWebhookExecutionProviderConfig. Correctly uses vi.hoisted and verifies the contextual error message format on failure.

Sequence Diagram

sequenceDiagram
    participant Caller
    participant Route as update-cost route
    participant Idempotency as billingIdempotency
    participant DB as recordUsage / DB

    Caller->>Route: POST /api/billing/update-cost (idempotencyKey?)
    Route->>Idempotency: atomicallyClaim('update-cost', key)
    alt key already exists
        Idempotency-->>Route: claimed=false
        Route-->>Caller: 409 Duplicate request
    else first time
        Idempotency-->>Route: claimed=true (in-progress stored)
        Route->>DB: recordUsage(...)
        alt recordUsage succeeds
            DB-->>Route: ok (usageCommitted=true)
            Route->>DB: checkAndBillOverageThreshold(...)
            alt threshold check succeeds
                Route-->>Caller: 200 success (key stays in-progress until TTL)
            else threshold check fails
                Route->>Idempotency: retain claim (prevent double-billing)
                Route-->>Caller: 500 error
            end
        else recordUsage fails
            Route->>Idempotency: release(normalizedKey) — retry allowed
            Route-->>Caller: 500 error
        end
    end

Loading

_{Reviews (1): Last reviewed commit: "fix(triggers): env var resolution in pro..." | Re-trigger Greptile}