.github: update new-release.md issue template.

Signed-off-by: Krisztian Litkey <[email protected]>

.github/ISSUE_TEMPLATE/new-release.md

@@ -36,6 +36,17 @@ future releases.
     - [ ] Get the change log OK'd by other maintainers.
   - [ ] Publish the draft as a release.
   - [ ] Verify that the Helm repo was updated
+    - ```
+      wget https://raw.githubusercontent.com/containers/nri-plugins/refs/heads/gh-pages/index.yaml
+      for i in nri-resource-policy-topology-aware nri-resource-policy-balloons nri-resource-policy-template nri-memory-qos nri-memtierd; do
+          if [ $(cat index.yaml | yq ".entries.$i[] | select(.version == \"$VERSION\") | length > 0") != "true" ]; then
+              echo "FAILED: Helm chart $i:$VERSION NOT FOUND"
+          else
+              echo "OK: $i"
+          fi
+      done
+      rm index.yaml
+      ```
   - [ ] Add a link to the tagged release in this issue.
   - [ ] Generate the operator bundle by running make bundle within `deployment/operator` directory and submit the generated content to the [community-operators](https://github.com/k8s-operatorhub/community-operators).
 - [ ] Create and push unannotated development tag `X.Y.0-devel` for next release cycle.