Skip to content

Conversation

@github-actions
Copy link
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.

github-actions bot and others added 2 commits December 16, 2025 20:20
* fix(app): add orgId query parameter to /api/cloud-tests/providers endpoint

* fix(app): add auth check to api/cloud-tests/providers endpoint

* fix(app): verify if the user belongs to the org in cloud-tests/provider endpoint

* fix(app): update cloud-tests/findings endpoint to have orgId as query param

---------

Co-authored-by: chasprowebdev <chasgarciaprowebdev@gmail.com>
Co-authored-by: Mariano Fuentes <marfuen98@gmail.com>
@vercel
Copy link

vercel bot commented Dec 16, 2025

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

Project Deployment Review Updated (UTC)
app (staging) Ready Ready Preview, Comment Dec 16, 2025 9:01pm
portal (staging) Ready Ready Preview, Comment Dec 16, 2025 9:01pm

@CLAassistant
Copy link

CLAassistant commented Dec 16, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Marfuen
❌ github-actions[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.

@cursor
Copy link

cursor bot commented Dec 16, 2025

PR Summary

Adds a Trigger.dev build extension and CI steps to include the workspace integration-platform, scopes cloud-tests API/UI by orgId with stricter auth, and always shows task automations when present.

  • Backend/API
    • Add integrationPlatformExtension to bundle @comp/integration-platform into Trigger.dev builds (apps/api/integrationPlatformExtension.ts) and register it in apps/api/trigger.config.ts.
    • Cloud tests endpoints now accept orgId via query, require membership, and merge new platform data with legacy:
      • GET /api/cloud-tests/findings: switches to NextRequest, validates user/org, fetches latest failed results from new integration* tables and legacy results, returns merged findings.
      • GET /api/cloud-tests/providers: validates user/org, reads manifests from @comp/integration-platform to compute required variables, returns new connections plus non-migrated legacy providers.
  • Frontend/UI
    • TestsLayout: SWR calls now include orgId in URLs; minor state/scan flows unchanged.
    • SingleTask: show Custom Automations whenever any exist, or if no mapped integration checks.
  • CI/CD
    • Workflows add install/build steps for packages/integration-platform across dev/prod deploys (API and app tasks).

Written by Cursor Bugbot for commit 912f418. This will update automatically on new commits. Configure here.

@graphite-app
Copy link

graphite-app bot commented Dec 16, 2025

Graphite Automations

"Auto-assign PRs to Author" took an action on this PR • (12/16/25)

1 reviewer was added to this PR based on Mariano Fuentes's automation.

* fix(app): update custom automations section to show based on conditions

* chore(api): add integration platform extension and update workflows
context.logger.log(
'Copied @comp/integration-platform to deployment bundle',
);
}
Copy link

Choose a reason for hiding this comment

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

Bug: Missing AWS SDK dependencies cause runtime deployment failures

The integrationPlatformExtension copies the @comp/integration-platform dist files to the Trigger.dev deployment but doesn't install its runtime dependencies. The integration-platform package (built with plain tsc, not bundled) requires @aws-sdk/client-cloudtrail and @aws-sdk/client-iam, which are not in apps/api/package.json and won't be available at runtime. Unlike the customPrismaExtension which uses context.addLayer() to ensure dependencies are installed, this extension only copies files. The deployment will fail at runtime when code tries to import these missing AWS SDK packages.

Fix in Cursor Fix in Web

* chore(workflows): add integration platform package installation and build steps
@Marfuen Marfuen merged commit 34fd713 into release Dec 16, 2025
13 of 15 checks passed
path: resolve(packagePath, 'dist', `${subpath}/index.js`),
};
},
);
Copy link

Choose a reason for hiding this comment

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

Bug: Subpath resolution incorrectly appends /index.js for flat exports

The subpath import resolution unconditionally appends /index.js to the subpath, which doesn't match the package's actual export structure. According to @comp/integration-platform's package.json, the ./types export maps to ./dist/types.js, not ./dist/types/index.js. When resolving @comp/integration-platform/types, the code produces dist/types/index.js instead of the correct dist/types.js. This would cause build failures if any Trigger.dev task imports from the /types subpath.

Fix in Cursor Fix in Web

@claudfuen
Copy link
Contributor

🎉 This PR is included in version 1.72.0 🎉

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.

4 participants