Skip to content

[comp] Production Deploy#3163

Merged
tofikwest merged 9 commits into
releasefrom
main
Jun 16, 2026
Merged

[comp] Production Deploy#3163
tofikwest merged 9 commits into
releasefrom
main

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.


Summary by cubic

Restores scheduled checks for dynamic integrations by delegating their runs to the API server and letting the scheduler read DB-backed check maps when no manifest exists. Also fixes @trycompai/mcp-server API‑key placeholders and tightens .gitignore.

  • Bug Fixes
    • Dynamic integrations now run automatically: the scheduler falls back to DB check→task mappings when no manifest is present; workers delegate dynamic providers to the API server (AWS unchanged); unknown providers still fail fast.
    • Docs and repo hygiene: replaced comp_…your_key_here… with comp_your_api_key_here in all @trycompai/mcp-server examples and added a troubleshooting note for U+2026 header errors; unanchored .gitignore rules to exclude dbq_*.js and *.csv at any depth.

Written for commit a86bc7b. Summary will update on new commits.

Review in cubic

tofikwest and others added 6 commits June 16, 2026 15:40
… footgun)

The API-key placeholder was `comp_…your_key_here…` using a literal ellipsis
(U+2026). Customers who copied it kept the `…`, and the MCP server then failed
to serialize the x-api-key header — Node throws "character at index 5 has a
value of 8230 which is greater than 255" on every tool call (customer-reported).

Replace every copy-paste placeholder with plain ASCII (`comp_your_api_key_here`),
drop the ellipsis from the surrounding prose, and add a troubleshooting entry for
the encoding error.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…y schedule

Dynamic (DB-backed) integrations — Keeper, Supabase, and ~575 others —
never ran on the daily schedule; they only ran on manual "Run" clicks.

Root cause: the orchestrator (integration-checks-schedule) and worker
(run-task-integration-checks) run in the Trigger.dev runtime, whose
manifest registry is seeded only with the 8 static code manifests. The
dynamic-manifest loader is a NestJS OnModuleInit service that never runs
there, so getManifest(dynamicSlug) returns undefined and the orchestrator
silently skipped those connections. Manual runs work because they execute
in the API process where the loader has populated the registry.

Fix (mirrors the existing AWS server-delegation):
- Orchestrator discovers dynamic task mappings straight from the DB
  (DynamicCheck.taskMapping / isEnabled) via resolveProviderChecks, so
  static providers still resolve from the code manifest and win when both
  exist.
- Worker + auto-run-on-connect delegate dynamic providers to the API
  server (runChecksOnServer → the provider-agnostic ConnectionCheckRunner),
  where the dynamic manifest is loaded. shouldRunOnServer = aws || (no
  local manifest && active dynamic). A truly unknown provider still
  early-returns instead of crashing.

Static integrations and AWS are unchanged (the in-process path only runs
when a manifest is present). Also fixes scheduled auto-run-on-connect for
dynamic providers.

Tests: new dynamic-provider.spec (shouldRunOnServer + isActiveDynamicProvider)
and resolveProviderChecks cases; 21 trigger/integration-platform tests pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(mcp): fix API-key placeholder encoding footgun (ellipsis in header)
@vercel

vercel Bot commented Jun 16, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
app (staging) Ready Ready Preview, Comment Jun 16, 2026 9:18pm
comp-framework-editor (staging) Ready Ready Preview, Comment Jun 16, 2026 9:18pm
portal (staging) Ready Ready Preview, Comment Jun 16, 2026 9:18pm

Request Review

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Re-trigger cubic

tofikwest and others added 3 commits June 16, 2026 16:58
Addresses cubic review on #3165: `/*.csv` and `/dbq_*.js` only matched
repo-root files, so an exported customer CSV or a creds-bearing ops script
in a subfolder could still be tracked. Drop the leading slash so the rules
apply at any depth. Verified zero `.csv`/`dbq_*.js` files are currently
tracked, so nothing legitimate is hidden or needs untracking.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…s-scheduled-runs

fix(integration-platform): run dynamic integration checks on the daily schedule
@claudfuen

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 3.83.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants