fix: vuln scan status type in projects_populated_ds

[epipav]

Note

Low Risk
No effective code changes were visible in the provided diff, so this appears to be a no-op PR with minimal risk.

Overview
No functional changes could be identified from the provided diff (it only shows +++ /dev/null with no file context or hunks). If this is unintended, re-export the full patch so reviewers can validate the intended projects_populated_ds vuln-scan status type fix.

^{Reviewed by Cursor Bugbot for commit 90f0c9a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[CLAassistant]

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 3 committers have signed the CLA.

✅ themarolt
❌ epipav
❌ gaspergrom
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[Copilot]

Pull request overview

Updates the Tinybird insights_projects_populated_ds datasource schema to correct the ClickHouse type of the aggregated vulnerability scan status field used by insights/analytics pipes that read from this datasource.

Changes:

• Changed lastVulnerabilityScanStatus column type from LowCardinality(Nullable(String)) to Nullable(String) in the datasource schema.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.