From 4c9a51b5069d309c739092a50dd1351c0aac2ed3 Mon Sep 17 00:00:00 2001 From: Steven Silvester Date: Mon, 11 Jul 2022 09:50:45 -0500 Subject: [PATCH] Backport PR #913: Fix handling of dev version --- .github/workflows/check-release.yml | 1 + RELEASE.md | 3 +++ 2 files changed, 4 insertions(+) diff --git a/.github/workflows/check-release.yml b/.github/workflows/check-release.yml index 441d7016ab..e602d474f7 100644 --- 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 index a785a28701..610aafe856 100644 --- 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: