[comp] Production Deploy by github-actions[bot] · Pull Request #2070 · trycompai/comp

github-actions · 2026-01-29T01:30:45Z

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.

* feat(api): add support for multiple connections in AWS integration * fix(api): improve error handling and connection activation logic * feat(cloud-tests): conditionally show "Add connection" button for providers * fix(api): enhance AWS credentials validation and improve connection handling * fix(integrations): improve success message for AWS connection * fix(integrations): prevent re-initialization of connection view on open * fix(api): merge existing credentials for AWS connection validation --------- Co-authored-by: Tofik Hasanov <annexcies@gmail.com>

vercel · 2026-01-29T01:30:51Z

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

Project	Deployment	Actions	Updated (UTC)
app (staging)	Ready	Preview, Comment	Jan 30, 2026 2:42pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
portal (staging)	Skipped		Jan 30, 2026 2:42pm

cursor · 2026-01-29T01:30:51Z

PR Summary

Medium Risk
Medium risk: changes connection creation/testing flows (including AWS STS/SecurityHub validation), adds a new daily Trigger.dev orchestrator, and introduces new bulk-delete and vendor-risk assessment behaviors that write to core tables.

Overview
Multi-connection cloud integrations (AWS-first). Providers now expose supportsMultipleConnections, and ConnectionService only enforces “one connection per org” when that flag is false. Connections can store/display metadata (connection name, regions, role/account info), and there’s a new PATCH /v1/integrations/connections/:id to update metadata.

AWS connection hardening + multi-region scanning. AWS connections are now validated before creation and before credential updates by assuming roles via SECURITY_HUB_ROLE_ASSUMER_ARN and verifying Security Hub is enabled in all selected regions; successful creates are immediately activated. AWS security scans now accept multiple regions, assume role once, scan each region, and tag findings with region in title/evidence for UI filtering.

New scheduled cloud security scans. Adds Trigger.dev tasks cloud-security-schedule (daily orchestrator) and run-cloud-security-scan (per-connection worker) to run scans for active connections whose manifest enables multi-connection support.

Task + vendor workflow updates. Adds DELETE /v1/tasks/bulk and a UI bulk-delete modal (API client delete now supports request bodies). Vendor risk assessment now supports internal single-vendor triggering with run tracking, UI realtime/skeleton progress, website editing, and AI-based normalization of assessment riskLevel into persisted inherent/residual probability/impact enums.

^{Written by Cursor Bugbot for commit 35a99c7. This will update automatically on new commits. Configure here.}

CLAassistant · 2026-01-29T01:30:53Z

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

apps/api/src/integration-platform/controllers/connections.controller.ts

apps/app/src/app/(app)/[orgId]/cloud-tests/components/TestsLayout.tsx

apps/app/src/components/integrations/ConnectIntegrationDialog.tsx

* feat(cloud-security): add daily scheduled task for cloud security scans * feat(cloud-security): enhance AWS region scanning with improved credential handling * refactor(cloud-security): improve error handling and logging in scan task * refactor(cloud-security): simplify primary region assignment in AWS service --------- Co-authored-by: Tofik Hasanov <annexcies@gmail.com>

apps/app/src/app/(app)/[orgId]/cloud-tests/components/EmptyState.tsx

* fix(app): remove device hosts when removing a member * fix(app): remove device hosts before deactivating the member * fix(app): remove devices from fleet before assignment clearing and member deactivation * fix(app): add null check on hosts array before mapping --------- Co-authored-by: chasprowebdev <chasgarciaprowebdev@gmail.com> Co-authored-by: Mariano Fuentes <marfuen98@gmail.com> Co-authored-by: chasprowebdev <70908289+chasprowebdev@users.noreply.github.com>

cursor · 2026-01-29T18:31:55Z

apps/app/src/app/(app)/[orgId]/people/all/actions/removeMember.ts

+            return fleet.delete(`/hosts/${hostId}`);
+          }));
+        }
+      }


FleetDM failure blocks member removal operation

Medium Severity

The new FleetDM integration code runs without error handling before the database cleanup operations. If getFleetInstance() fails (e.g., missing FLEET_URL/FLEET_TOKEN environment variables) or any of the FleetDM API calls fail (network issues, service unavailable, invalid label ID), the entire member removal operation fails. This prevents removing members from the organization when FleetDM is misconfigured or unavailable, even though FleetDM cleanup is not essential to the core operation of deactivating a member.

apps/app/src/app/api/cloud-tests/providers/route.ts

* feat(vendor): implement risk assessment triggering and update schemas * feat(vendor): handle failure states in risk assessment run * feat(tasks): add bulk delete endpoint for tasks and corresponding UI * feat(vendor): implement AI-based normalization for risk levels --------- Co-authored-by: Tofik Hasanov <annexcies@gmail.com>

apps/app/src/app/(app)/[orgId]/vendors/[vendorId]/actions/trigger-vendor-risk-assessment.ts

cursor · 2026-01-29T22:43:12Z

apps/api/src/trigger/vendor/vendor-risk-assessment-task.ts

+      return Impact.moderate;
+  }
+}
+


Duplicated normalizeWebsite and extractDomain utility functions

Low Severity

The normalizeWebsite and extractDomain functions are duplicated in three locations: apps/app/src/utils/normalize-website.ts (the shared utility), apps/api/src/vendors/vendors.service.ts, and apps/api/src/trigger/vendor/vendor-risk-assessment-task.ts. The implementations are identical. The API-side code could either import from a shared package or create a single utility file in the API package rather than duplicating these functions.

Additional Locations (1)

apps/api/src/vendors/vendors.service.ts#L9-L54

Co-authored-by: Tofik Hasanov <annexcies@gmail.com>

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-01-30T13:23:38Z

apps/api/src/integration-platform/controllers/connections.controller.ts

      await this.connectionService.activateConnection(id);
+      this.logger.log(
+        `Activated connection ${id} after credential update (was in error state)`,
+      );


Paused connections incorrectly activated on credential update

Medium Severity

The comment states "Only activate the connection if it was in error state (don't resume paused connections)" but this behavior isn't achieved. The storeApiKeyCredentials method (called at line 1052) unconditionally sets the connection status to 'active' internally before the status check at line 1058 can execute. This means paused connections will be unexpectedly resumed when a user updates credentials like regions, contrary to the documented intent.

* fix(docs): remove redundant setup steps from Aikido integration guide * style(trust): update text color for domain alert message --------- Co-authored-by: Tofik Hasanov <annexcies@gmail.com>

claudfuen · 2026-01-30T14:50:18Z

🎉 This PR is included in version 1.80.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

github-actions bot added prod-deploy automated-pr labels Jan 29, 2026

vercel bot deployed to staging – app January 29, 2026 01:31 View deployment

vercel bot deployed to staging – portal January 29, 2026 01:32 View deployment

cursor bot reviewed Jan 29, 2026

View reviewed changes

vercel bot temporarily deployed to staging – portal January 29, 2026 04:44 Inactive

vercel bot deployed to staging – app January 29, 2026 04:46 View deployment

cursor bot reviewed Jan 29, 2026

View reviewed changes

apps/app/src/app/(app)/[orgId]/cloud-tests/components/EmptyState.tsx Show resolved Hide resolved

vercel bot temporarily deployed to staging – portal January 29, 2026 18:19 Inactive

vercel bot deployed to staging – app January 29, 2026 18:21 View deployment

cursor bot reviewed Jan 29, 2026

View reviewed changes

vercel bot temporarily deployed to staging – portal January 29, 2026 22:30 Inactive

mintlify bot deployed to staging - packages/docs January 29, 2026 22:31 View deployment

vercel bot deployed to staging – app January 29, 2026 22:32 View deployment

cursor bot reviewed Jan 29, 2026

View reviewed changes

feat(docs): add Aikido integration guide and related images (#2076)

cb861f9

Co-authored-by: Tofik Hasanov <annexcies@gmail.com>

vercel bot temporarily deployed to staging – portal January 30, 2026 13:11 Inactive

vercel bot temporarily deployed to staging – app January 30, 2026 13:11 Inactive

mintlify bot deployed to staging - packages/docs January 30, 2026 13:12 View deployment

cursor bot reviewed Jan 30, 2026

View reviewed changes

[dev] [tofikwest] tofik/fix-documentation (#2078)

35a99c7

* fix(docs): remove redundant setup steps from Aikido integration guide * style(trust): update text color for domain alert message --------- Co-authored-by: Tofik Hasanov <annexcies@gmail.com>

vercel bot temporarily deployed to staging – portal January 30, 2026 14:40 Inactive

vercel bot deployed to staging – app January 30, 2026 14:42 View deployment

mintlify bot deployed to staging - packages/docs January 30, 2026 14:44 View deployment

tofikwest merged commit 3fe1d31 into release Jan 30, 2026
12 of 13 checks passed

claudfuen added the released label Jan 30, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[comp] Production Deploy#2070

[comp] Production Deploy#2070
tofikwest merged 6 commits intoreleasefrom
main

github-actions bot commented Jan 29, 2026

Uh oh!

vercel bot commented Jan 29, 2026 •

edited

Loading

Uh oh!

cursor bot commented Jan 29, 2026 •

edited

Loading

Uh oh!

CLAassistant commented Jan 29, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursor bot Jan 29, 2026

Uh oh!

Uh oh!

Uh oh!

cursor bot Jan 29, 2026

Uh oh!

cursor bot left a comment

Uh oh!

cursor bot Jan 30, 2026

Uh oh!

Uh oh!

claudfuen commented Jan 30, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

github-actions bot commented Jan 29, 2026

Uh oh!

vercel bot commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cursor bot commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

Uh oh!

CLAassistant commented Jan 29, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursor bot Jan 29, 2026

Choose a reason for hiding this comment

FleetDM failure blocks member removal operation

Uh oh!

Uh oh!

Uh oh!

cursor bot Jan 29, 2026

Choose a reason for hiding this comment

Duplicated normalizeWebsite and extractDomain utility functions

Uh oh!

cursor bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor bot Jan 30, 2026

Choose a reason for hiding this comment

Paused connections incorrectly activated on credential update

Uh oh!

Uh oh!

claudfuen commented Jan 30, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

vercel bot commented Jan 29, 2026 •

edited

Loading

cursor bot commented Jan 29, 2026 •

edited

Loading