Update the the release checklist

.github/ISSUE_TEMPLATE/new_release_checklist.md

@@ -8,7 +8,6 @@ Since the dev branch only includes materials that have been peer-reviewed at lea
 * Open a PR into main branch, it should be titled with the new release number  
 * Let Leeyabot generate a report detailing how the Hector output has changed! 
 * Add text to the PR documenting the major model changes. The PR is going to serve as an important record 
-* Update the outputstreams via command line & commit them as part of the PR 
 * Pass automated checks
 * Change the version number in the DESCRIPTION file 
 * Update the NEWS.md, are links additional materials necessary? Does the release need a new naming file? 
@@ -19,4 +18,5 @@ After merging PR
 * Create the release via zenodo 
 * Add the zenodo links to README / NEWS & push directly to main 
 * Create new dev branch & update the DESCRIPTION version number to support the pkgdown documentation for the developmental branch!
+* Add archived outputstreams to release assets!