make post release more promiment (#3497)

Author: elchead

dev-docs/workflows/release.md

@@ -46,6 +46,8 @@ Releases should be performed using [the automated release pipeline](https://gith
 6. look over the autogenerated draft release. When fixing the changelog, prioritize updating the PR title/labels/description and regenerating the changelog over fixing things in the final changelog. The changelog should be primarily aimed at users. Rule of thumb: first part of the sentence should describe what changed for the user, second part can describe what has been changed to achieve this.
 7. in the GitHub release UI, make sure the tag to create on release is set to `$ver`, and the target commit is set to the temporary release branch.
 8. publish.
+9. follow [post release steps](#post-release-steps).
+
 
 ### Minor release
 
@@ -78,6 +80,7 @@ Releases should be performed using [the automated release pipeline](https://gith
 8. set the Target to `tmp/${ver}`
 9. in the GitHub release UI, make sure the tag to create on release is set to `$ver`, and the target commit is set to the temporary release branch.
 10. publish.
+11. follow [post release steps](#post-release-steps).
 
 ## Post release steps