Merge pull request #131 from datalayer-externals/fix/check-release-de…

…v-version

Fix handling of dev version when releasing

.github/workflows/check-release.yml

@@ -50,6 +50,7 @@ jobs:
         if: ${{ matrix.group == 'check_release' }}
         uses: jupyter-server/jupyter_releaser/.github/actions/check-release@v1
         with:
+          version_spec: 100.100.100
           token: ${{ secrets.GITHUB_TOKEN }}
       - name: Run Link Check
         if: ${{ matrix.group == 'link_check' }}

RELEASE.md

@@ -1,3 +1,14 @@
+# Making a NbClassic Release
+
+## Using `jupyter_releaser`
+
+The recommended way to make a release is to use [`jupyter_releaser`](https://github.com/jupyter-server/jupyter_releaser#checklist-for-adoption).
+
+Note that we must use manual versions since Jupyter Releaser does not
+yet support "next" or "patch" when dev versions are used.
+
+## Manual Release
+
 To create a release, update the version number in `nbclassic/__version__.py`, then run the following:
 
 ```