chore: update links generated by check releases script (#8679)

* chore: add dynamic npm link to check releases script * make link open in new tab * update releases link
vaadin · Feb 14, 2025 · b98f1e9 · b98f1e9
1 parent 62a0c6d
commit b98f1e9
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/scripts/check-releases.template.html b/scripts/check-releases.template.html
@@ -156,7 +156,9 @@ <h3>Step 1: Release web components</h3>
                 <li>Confirm if a dialog asks about using an auto-generated branch name</li>
                 <li
                   >Wait for the build to finish, then check that new versions have appeared on NPM (e.g.
-                  <a href="https://www.npmjs.com/package/@vaadin/grid">https://www.npmjs.com/package/@vaadin/grid</a>)
+                  <a href="https://www.npmjs.com/package/@vaadin/grid/v/${this.branch.nextPatchVersion}" target="_blank"
+                    ><code>@vaadin/grid@${this.branch.nextPatchVersion}</code></a
+                  >)
                 </li>
               </ul>
             </section>
@@ -205,11 +207,9 @@ <h3>Step 2: Release API docs</h3>
               <h3>Step 3: Publish GitHub Release</h3>
               <ul>
                 <li>
-                  <a
-                    href="https://github.com/vaadin/web-components/releases/edit/v${this.branch.nextPatchVersion}"
-                    target="_blank"
-                    >Edit the GitHub release created in Step 1</a
-                  >
+                  <a href="https://github.com/vaadin/web-components/releases" target="_blank"
+                    >Open the GitHub releases and edit the <code>v${this.branch.nextPatchVersion}</code> draft release
+                  </a>
                 </li>
                 <li>Check that the documentation link works</li>
                 <li>Check that the contents are correct</li>