From 4caff487bf88f10faed31c78b241c9dad9bc67f2 Mon Sep 17 00:00:00 2001
From: Eric Charles <eric@datalayer.io>
Date: Mon, 11 Jul 2022 17:00:11 +0200
Subject: [PATCH] fix handling of dev version when releasing

---
 .github/workflows/check-release.yml |  1 +
 RELEASE.md                          | 11 +++++++++++
 2 files changed, 12 insertions(+)

diff --git a/.github/workflows/check-release.yml b/.github/workflows/check-release.yml
index 3a4fa8008..3b2a1ed3e 100644
--- a/.github/workflows/check-release.yml
+++ b/.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' }}
diff --git a/RELEASE.md b/RELEASE.md
index eea99a8d1..9bcdc4f29 100644
--- a/RELEASE.md
+++ b/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:
 
 ```