(historic one) you fork the jupyter_releaser and execute actions to release package from that fork to carry release; this is what I'm using to release Lumino and JupyterLab for example - see my fork action
(new recommended one) you set GitHub actions directly in the package; this is what is configured for jupyter-server for example.
Would you be willing to update the template to use the new recommended way?
Description
Hi, in RELEASE.md, the typical workflow section of jupyter_releaser is referenced, but that section was removed.
Should it point to the How-to Guides?
Maybe an additional remark: I don't fully understand the Convert a Repo to Use Releaser from Releaser and Convert a Repo to Use Releaser from Repo headlines. Reading the steps, is the