Pipeline/testing new chart releases

[DiamondJoseph]

I'm deploying renovate with ArgoCD from a repository on a self-hosted gitlab instance.
Argo watches the repository which contains my Chart.yaml and values.yaml and updates out of date resources on the cluster.
When renovate runs, it also checks the same repository and makes PRs to update the Chart.yaml version.

This is the fastest moving of the repositories I'm currently watching with renovate, and I'd like to add a pipeline to make sure e.g. my values.yaml is still valid, the loaded config is as expected, and the expected repositories are checked. If this were the case I'd then be able to set automerge with some degree of certainty, and only need to inspect the PR when the pipeline failed.

Currently I click through the source link in the PR which leads to this repository, then through to the renovatebot/renovate repository to see the changelog for the container before signing off on the changes.

Does anyone have something like this already?
I don't think helm test would work as it's expecting the resource (i.e. the pod) to be available for prodding.
I could set up a parallel Argo app targeting a branch, but the branch name is dependent on the new version.
helm lint and helm install --dry-run don't catch keys no longer being in use (do they catch deprecated keys?) or changes to config (although I'd expect those to be major changes)