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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 10, 2026 7:44pm

PR Summary

Low Risk
Low risk, small change to resolveDependencyValue that only alters behavior when canonical resolution yields null/undefined, primarily affecting dependsOn gating/visibility for trigger-mode subblocks in canonical groups.

Overview
Fixes dependsOn gating for trigger-mode subblocks that share canonical groups with block subblocks by updating resolveDependencyValue to fall back to values[dependencyKey] when the canonically-resolved value is null/undefined.

This prevents trigger fields from staying disabled when their IDs aren’t the canonical group’s basicId/advancedId, while leaving normal canonical swaps unchanged when they successfully resolve a value.

^{Reviewed by Cursor Bugbot for commit bb721c9. Configure here.}

Greptile Summary

This PR fixes a dependsOn gating regression for trigger-mode subblocks (e.g. Google Sheets spreadsheetId picker staying disabled after selecting credentials). The root cause was that resolveDependencyValue resolved triggerCredentials through the canonical group (oauthCredential), whose basicId is the regular block's credential subblock — so values['credential'] is always undefined in trigger mode, causing the resolved value to be undefined and the downstream field to remain disabled.

The fix is a one-line ?? values[dependencyKey] fallback: if canonical resolution returns nothing (null/undefined), fall back to the raw value for the dependency key itself. This correctly handles the trigger case without affecting regular block behavior, since canonical resolution only returns null/undefined when basicId and all advancedIds are empty in the current values — a state that can only arise when the dependency key is a trigger-mode subblock that isn't the group's basicId.

Confidence Score: 5/5

Safe to merge — targeted one-line fix with no regression risk for regular blocks.

The change is a single nullish-coalescing fallback in resolveDependencyValue. The fallback only activates when canonical resolution returns null/undefined, which only happens when the dependency key is a trigger-mode subblock not registered as basicId in its canonical group. For all regular block subblocks the canonical result is always the actual stored value, so the fallback never fires. No P0/P1 findings were identified.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["resolveDependencyValue(dependencyKey, values, canonicalIndex)"] --> B{canonicalId found?}
    B -- No --> C["return values[dependencyKey]"]
    B -- Yes --> D{group found?}
    D -- No --> C
    D -- Yes --> E["getCanonicalValues(group, values)"]
    E --> F["resolveCanonicalMode(group, values, overrides)"]
    F --> G{"mode === 'advanced'?"}
    G -- Yes --> H["canonicalResult = advancedValue ?? basicValue"]
    G -- No --> I["canonicalResult = basicValue ?? advancedValue"]
    H --> J{canonicalResult null/undefined?}
    I --> J
    J -- No --> K["return canonicalResult"]
    J -- Yes --> L["return values[dependencyKey]"]
    L --> M["Trigger mode: returns values['triggerCredentials']"]

_{Reviews (1): Last reviewed commit: "fix(trigger): resolve dependsOn for trig..." | Re-trigger Greptile}