Conversation
) - Remove Geist font @font-face from all 12 email templates. Email clients block external fonts anyway, and the references created unnecessary connections to app.trycomp.ai from email context. - Delete waitlist.tsx template and lib (dead code, no longer used) - Clean up barrel exports in packages/email/index.ts Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
PR SummaryMedium Risk Overview On Separately, Trigger.dev configs drop Reviewed by Cursor Bugbot for commit 56c67df. Bugbot is set up for automated code reviews on this repo. Configure here. |
…in people tab * fix(app): check FleetDM device compliance alongside new device agent The people tab DEVICE column previously only checked the new device agent. Now it also checks FleetDM (legacy) so members using either agent show correct compliance status: Compliant, Non-Compliant, or Not Installed. Device agent takes priority when both are present. The devices tab compliance chart now includes both sources in its totals. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(app): unify device compliance logic between member list and chart Move device status computation from TeamMembers into page.tsx where fleet host data (with Fleet API automated checks + DB manual overrides) is already fetched. This ensures the member list DEVICE column and the compliance chart use identical data and compliance logic. Previously TeamMembers only checked FleetPolicyResult DB records, missing Fleet API automated policy checks. A device passing Fleet's automated check but lacking a DB override would show "Non-Compliant" in the member list but "Compliant" in the chart. Also fixes a bug where multiple fleet devices for the same member could not downgrade status from compliant to non-compliant. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Mariano Fuentes <marfuen98@gmail.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Trigger.dev manages its own env vars independently. All required vars are already set in Trigger's dashboard for both staging and production. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Mariano Fuentes <marfuen98@gmail.com>
|
🎉 This PR is included in version 3.20.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.