Sync repo templates ⚙

Sync with coreos/repo-templates@e909d87.

.github/ISSUE_TEMPLATE/release-checklist.md

@@ -32,7 +32,8 @@ Push access to the upstream repository is required in order to publish the new t
 
 - make sure the project is clean and prepare the environment:
   - [ ] Make sure `cargo-release` and `cargo-vendor-filterer` are up to date: `cargo install cargo-release cargo-vendor-filterer`
-  - [ ] `cargo test --all-features`
+  - [ ] `cargo vendor-filterer target/vendor`
+  - [ ] `cargo test --all-features --config 'source.crates-io.replace-with="vv"' --config 'source.vv.directory="target/vendor"'`
   - [ ] `cargo clean`
   - [ ] `git clean -fd`
   - [ ] `RELEASE_VER=x.y.z`
@@ -84,13 +85,13 @@ Push access to the upstream repository is required in order to publish the new t
   - [ ] run `kinit your_fas_account@FEDORAPROJECT.ORG`
   - [ ] run `fedpkg new-sources $(spectool -S rust-zincati.spec | sed 's:.*/::')`
   - [ ] PR the changes in [Fedora](https://src.fedoraproject.org/rpms/rust-zincati)
-  - [ ] once the PR merges to rawhide, merge rawhide into the other relevant branches (e.g. f35) then push those, for example:
+  - [ ] once the PR merges to rawhide, merge rawhide into the other relevant branches (e.g. f38) then push those, for example:
     ```bash
     git checkout rawhide
     git pull --ff-only
-    git checkout f35
+    git checkout f38
     git merge --ff-only rawhide
-    git push origin f35
+    git push origin f38
     ```
   - [ ] on each of those branches run `fedpkg build`
   - [ ] once the builds have finished, submit them to [bodhi](https://bodhi.fedoraproject.org/updates/new), filling in: