Backport PR #913 on branch 1.x (Fix handling of dev version) (#914)

Co-authored-by: Steven Silvester <steven.silvester@ieee.org>
jupyter-server · Jul 11, 2022 · 98db236 · 98db236
1 parent 04b197d
commit 98db236
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/.github/workflows/check-release.yml b/.github/workflows/check-release.yml
@@ -22,6 +22,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
@@ -4,6 +4,9 @@
 
 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 manual release, perform the following steps: