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

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

.github/ISSUE_TEMPLATE/new-release.md

@@ -26,16 +26,21 @@ future releases.
   - [ ] Push the tag with `git push $VERSION`.
   - [ ] Check that new container images are published for the tag.
     - ```
-      for i in nri-resource-policy-topology-aware nri-resource-policy-balloons nri-resource-policy-template nri-config-manager nri-memory-qos nri-memtierd; do \
-          skopeo inspect --format "$i: {{.Digest}}" docker://ghcr.io/containers/nri-plugins/$i:$VERSION;
-      done
+      # You can do this with the in-repo artifact verification script:
+      ./scripts/release/check-artifacts.sh --images $VERSION
       ```
   - [ ] Finalize the new *draft* release created by CI
     - [ ] Check that all artefacts (Helm charts) were uploaded
     - [ ] Write the change log to the release.
     - [ ] Get the change log OK'd by other maintainers.
   - [ ] Publish the draft as a release.
   - [ ] Verify that the Helm repo was updated
+    - ```
+      # You can do this with the in-repo artifact verification script:
+      ./scripts/release/check-artifacts.sh --charts $VERSION
+      # Or to do a final verification of both images and charts:
+      ./scripts/release/check-artifacts.sh $VERSION
+      ```
   - [ ] 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.