Skip to content

Commit 9dc59f9

Browse files
authored
Merge pull request #131 from datalayer-externals/fix/check-release-dev-version
Fix handling of dev version when releasing
2 parents 7ea5af3 + 4caff48 commit 9dc59f9

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

.github/workflows/check-release.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,7 @@ jobs:
5050
if: ${{ matrix.group == 'check_release' }}
5151
uses: jupyter-server/jupyter_releaser/.github/actions/check-release@v1
5252
with:
53+
version_spec: 100.100.100
5354
token: ${{ secrets.GITHUB_TOKEN }}
5455
- name: Run Link Check
5556
if: ${{ matrix.group == 'link_check' }}

RELEASE.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,14 @@
1+
# Making a NbClassic Release
2+
3+
## Using `jupyter_releaser`
4+
5+
The recommended way to make a release is to use [`jupyter_releaser`](https://github.com/jupyter-server/jupyter_releaser#checklist-for-adoption).
6+
7+
Note that we must use manual versions since Jupyter Releaser does not
8+
yet support "next" or "patch" when dev versions are used.
9+
10+
## Manual Release
11+
112
To create a release, update the version number in `nbclassic/__version__.py`, then run the following:
213

314
```

0 commit comments

Comments
 (0)