Skip to content

fix(integrations): show catalog-wired connectors as beta - #230

Open
sdhilip200 wants to merge 2 commits into
cabinetai:mainfrom
sdhilip200:codex/integrations-hub-visibility
Open

fix(integrations): show catalog-wired connectors as beta#230
sdhilip200 wants to merge 2 commits into
cabinetai:mainfrom
sdhilip200:codex/integrations-hub-visibility

Conversation

@sdhilip200

Copy link
Copy Markdown
Contributor

Summary

  • show MCP catalog-wired integrations as connectable beta entries instead of Coming soon
  • keep integrations with no catalog wiring in the request-only flow
  • expose connectionStatus from the catalog API and refresh hub connection state on focus

Testing

  • npm run lint
  • npx tsc --noEmit
  • npm run build

Refs #198

@sdhilip200
sdhilip200 requested a review from a team as a code owner July 14, 2026 04:23
@oxedom

oxedom commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

@copilot resolve the merge conflicts in this pull request

@sdhilip200
sdhilip200 force-pushed the codex/integrations-hub-visibility branch from 64fdff0 to 11fddd3 Compare July 26, 2026 20:30
@sdhilip200

Copy link
Copy Markdown
Contributor Author

Rebased onto current \ and resolved the conflicts in the MCP catalog route and integrations gallery import block. Force-pushed the updated branch. I wasn’t able to run local lint/type verification in this worktree because the repo checkout here does not have installed Node dependencies.

@sdhilip200

Copy link
Copy Markdown
Contributor Author

Fixed the failing build issue from the July 26, 2026 CI run by restoring the missing \ import used by the beta badge in integration detail pages. I verified the patch with . I also attempted a clean local , but this machine is on Node 26 and the install failed in native dependency setup before the app build step; GitHub CI should be the authoritative verification for this branch because it runs under Node 22.

@sdhilip200

Copy link
Copy Markdown
Contributor Author

Fixed the missing Sparkles import used by the beta badge in the integration detail page and pushed the update to this PR branch. I verified the patch with git diff --check. I could not complete a full local npm install on this machine because the local environment is on Node 26 and hits a native-module setup issue, so the refreshed GitHub CI run will be the authoritative verification.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants