Skip to content

feat(trigger): add Google Sheets, Drive, and Calendar polling triggers #14208

feat(trigger): add Google Sheets, Drive, and Calendar polling triggers

feat(trigger): add Google Sheets, Drive, and Calendar polling triggers #14208

Triggered via pull request April 10, 2026 01:24
Status Failure
Total duration 1m 28s
Artifacts

ci.yml

on: pull_request
Detect Version
0s
Detect Version
Check Docs Changes
0s
Check Docs Changes
Test and Build  /  Test and Build
1m 18s
Test and Build / Test and Build
Matrix: Build AMD64
Matrix: Build ARM64 (GHCR Only)
Process Docs  /  Process Documentation Embeddings
Process Docs / Process Documentation Embeddings
Matrix: Create GHCR Manifests
Create GitHub Release
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 5 warnings
Test and Build / Test and Build
Process completed with exit code 1.
blocks/blocks.test.ts > Blocks Module > Canonical Param Validation > should have consistent required status across canonical param groups: apps/sim/blocks/blocks.test.ts#L1048
Error: Required status consistency errors: Block "google_sheets_v2": canonical param "spreadsheetId" has inconsistent required status. Required: [spreadsheetId (trigger), manualSpreadsheetId (trigger-advanced)], Optional: [spreadsheetId (basic), manualSpreadsheetId (advanced)]. All subBlocks in a canonical group should have the same required status. ❯ blocks/blocks.test.ts:1048:15
blocks/blocks.test.ts > Blocks Module > Canonical Param Validation > should have inputs containing canonical param IDs instead of raw subBlock IDs: apps/sim/blocks/blocks.test.ts#L930
Error: Inputs section validation errors: Block "google_drive": inputs section is missing canonical param "folderId" ❯ blocks/blocks.test.ts:930:15
blocks/blocks.test.ts > Blocks Module > Canonical Param Validation > should have unique canonicalParamIds per operation/condition context: apps/sim/blocks/blocks.test.ts#L886
Error: Canonical param reuse across conditions: Block "google_calendar": Canonical param "calendarId" is used across 2 different conditions. Each operation should have its own unique canonicalParamId. Block "google_calendar_v2": Canonical param "calendarId" is used across 2 different conditions. Each operation should have its own unique canonicalParamId. Block "google_sheets_v2": Canonical param "spreadsheetId" is used across 2 different conditions. Each operation should have its own unique canonicalParamId. Block "google_sheets_v2": Canonical param "sheetName" is used across 2 different conditions. Each operation should have its own unique canonicalParamId. ❯ blocks/blocks.test.ts:886:15
blocks/blocks.test.ts > Blocks Module > Canonical Param Validation > should have properly formed canonical pairs (matching conditions): apps/sim/blocks/blocks.test.ts#L845
Error: Canonical pair validation errors: Block "google_calendar": Canonical param "calendarId" has members with different conditions: {"field":"operation","value":"list_calendars","not":true} vs Block "google_calendar_v2": Canonical param "calendarId" has members with different conditions: {"field":"operation","value":"list_calendars","not":true} vs Block "google_drive": Canonical param "folderId" has no basic or advanced mode members Block "google_sheets_v2": Canonical param "spreadsheetId" has members with different conditions: {"field":"operation","value":"create","not":true} vs Block "google_sheets_v2": Canonical param "sheetName" has members with different conditions: {"field":"operation","value":["read","write","update","append","clear"]} vs ❯ blocks/blocks.test.ts:845:15
blocks/blocks.test.ts > Blocks Module > SubBlock Validation > should have valid mode values for subBlocks: apps/sim/blocks/blocks.test.ts#L430
AssertionError: expected [ 'basic', 'advanced', 'both', …(2) ] to include 'trigger-advanced' ❯ blocks/blocks.test.ts:430:30
Test and Build / Test and Build
sim#test: command (/home/runner/_work/sim/sim/apps/sim) /home/runner/.bun/bin/bun run test exited (1)
Test and Build / Test and Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test and Build / Test and Build
Skipping sticky disk commit due to previous step failures
Test and Build / Test and Build
Found 2 failed/cancelled steps in previous workflow steps
Test and Build / Test and Build
Skipping sticky disk commit due to previous step failures
Test and Build / Test and Build
Found 2 failed/cancelled steps in previous workflow steps