Swap image bump CI to dispatch strategy

[Angelin01]

Swaps to a dispatch strategy for image bumps, much simpler.

Validated in #25

[Copilot]

🟡 Changes recommended

The workflow can currently fail or behave unsafely when VERSION is missing/invalid (shell interpolation + “nothing to commit” path), and should validate inputs and handle no-op bumps cleanly.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR switches the image bump automation for the ccv-cell Helm chart from a scheduled “poll for latest tag” workflow to an explicit dispatch-driven workflow, where a caller supplies the target image tag/version.

Changes:

• Replace the hourly cron trigger with repository_dispatch (image-bump) and add a workflow_dispatch input (version).
• Simplify the workflow to directly set aggregator/verifier image tags to the provided version and open a PR.

File summaries

File	Description
.github/workflows/helm-ccv-cell-image-bump.yml	Move to dispatch-based bumping and simplify PR creation logic by taking an explicit VERSION input/payload.

Review details

Suppressed comments (1)

.github/workflows/helm-ccv-cell-image-bump.yml:56

• If the requested ${VERSION} is already present in values.yaml, git commit will fail with "nothing to commit" (because this workflow no longer gates on needs_bump), causing the whole run to fail. Add a guard that exits successfully when no diff is produced after the sed updates.

          git add "$VALUES"
          git commit -m "bump ccv images to ${VERSION}"
          git push origin "$branch"

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[khalifaa55]

Why are we setting the same tag for the aggregator and verifier?

[Angelin01]

Why are we setting the same tag for the aggregator and verifier?

Unfortunately, just matching the behavior from upstream at the moment. GCP Marketplace kind-of requires all tags to be the same, and upstream is going to release like that for now. So I matched it here for simplicity.

See this step: https://github.com/smartcontractkit/chainlink-ccv/blob/main/.github/workflows/release-publish.yaml#L64-L97

All use the same ${{ github.ref_name }} for the version