ci: ensure velero task renovate datasource matches chart#2645
Conversation
Greptile SummaryThis PR updates the Renovate annotation on
Confidence Score: 4/5The datasource change is correct and achieves the stated goal, but the existing version mismatch between tasks.yaml (12.0.0) and common/zarf.yaml (12.0.1) means the update-crds task will pull wrong CRDs until the default is bumped. The annotation itself is straightforward and well-reasoned, but the default version in tasks.yaml (12.0.0) still trails the deployed chart version (12.0.1) in common/zarf.yaml, leaving the CRD download task pointing at a stale chart tag. src/velero/tasks.yaml — the VELERO_CRD_VERSION default needs to be bumped to 12.0.1 to match the chart Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Renovate Bot] -->|Before: datasource=github-tags| B[vmware-tanzu/helm-charts GitHub Tags]
A -->|After: datasource=helm| C[vmware-tanzu Helm Registry]
B -->|Updates VELERO_CRD_VERSION in tasks.yaml| D[tasks.yaml VELERO_CRD_VERSION]
C -->|Updates VELERO_CRD_VERSION in tasks.yaml| D
C -->|Also updates version in common/zarf.yaml| E[common/zarf.yaml chart version]
D -->|Used to download CRDs from upstream| F[update-crds task]
E -->|Deployed chart version| G[Velero Helm Chart Install]
D -.->|Should match| E
style B fill:#f88,stroke:#c44
style C fill:#8f8,stroke:#4c4
Reviews (1): Last reviewed commit: "Update tasks.yaml" | Re-trigger Greptile |
Description
Noted in #2635 and #2613 that Velero's chart is updating at a different cadence than the task (which controls CRDs).
This updates the renovate comment to use the identical datasource as the chart reference (helm) in order to ensure these should always update in the same PR.