fix(fullsend): bump reusable dispatch workflow

[johnmcollier]

Description

This updates the Fullsend reusable dispatch workflow pin in .github/workflows/fullsend.yaml to a newer released Fullsend commit.

The previous fix added allowed_remote_resources to .fullsend/config.yaml, but the repository workflow was still pinned to an older reusable-dispatch.yml revision that predates the per-repo config loading fixes. As a result, rerunning Fullsend triage could still fail with the same allowed_remote_resources error even after the config change merged.

Changes

• bump fullsend-ai/fullsend/.github/workflows/reusable-dispatch.yml from 32f73a4f93301493d2c31be3970aa4c51a26acc7 to e22a1eff69ae1e1a4ac1b19927b5c8d4660b0ae7 (v0.29.0)

Testing

• Tested locally
• Not tested locally, because this is a GitHub Actions workflow pin change

Checklist

• Added/updated tests if needed, or explained why not needed
• This PR is not a docs-only change
• This change is scoped to fixing the still-failing Fullsend triage workflow

Made with Cursor

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rhdh-qodo-merge]

Code Review by Qodo

Sorry, something went wrong

We weren't able to complete the code review on our side. Please try again

[rhdh-qodo-merge]

PR Summary by Qodo

Fix Fullsend triage by bumping reusable dispatch workflow pin

🐞 Bug fix ⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Update Fullsend reusable-dispatch workflow pin to v0.29.0 to honor per-repo config.
• Prevent triage reruns from failing on allowed_remote_resources with older workflow revision.

Diagram

graph TD
  A["Repo workflow"] --> B["Reusable dispatch (pinned)"] --> C["Fullsend triage run"] --> D["Per-repo .fullsend/config"]
  subgraph Legend
    direction LR
    _wf["Workflow"] ~~~ _ext["External workflow"]
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Pin to a semver tag (e.g., v0.29.0) instead of commit SHA

• ➕ More readable and easier to audit/update
• ➕ Can align with release notes directly
• ➖ Tag movement risk if tags are not immutable (depends on publisher practices)
• ➖ Commit SHA pin provides strongest supply-chain immutability

2. Track a floating ref (keep @v0 for reusable workflow too)

• ➕ Automatic receipt of fixes without manual bumps
• ➕ Less maintenance overhead
• ➖ Higher change risk on every run; harder to correlate failures to changes
• ➖ Can introduce breaking behavior without a PR review window

Recommendation: This PR’s approach (pinning the reusable workflow to a known-good released commit) is the safest and most reviewable way to restore triage reliability. A semver tag pin could be acceptable if the upstream guarantees immutable tags, but commit SHA pinning remains the most robust option for CI supply-chain hygiene.

Files changed (1) +1 / -1

Other (1) +1 / -1

fullsend.yamlBump Fullsend reusable-dispatch workflow pin to v0.29.0 +1/-1

Bump Fullsend reusable-dispatch workflow pin to v0.29.0

• Updates the 'uses:' reference for the Fullsend reusable dispatch workflow from an older commit to 'e22a1eff...' (v0.29.0). This ensures triage runs use the revision that correctly loads per-repo configuration (including 'allowed_remote_resources').

.github/workflows/fullsend.yaml