Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During the minor release yesterday, The dreft chenglog has been create by https://github.com/echarles/jupyter_releaser/actions/runs/2624849537 and I have merged #124
Then I have run the full release https://github.com/echarles/jupyter_releaser/runs/7220840309?check_suite_focus=true and it has failed on the check_changelog step with the error (see (*) at the end of this comment). I have not been able to nail down the root of the issue, so I have decided to skip that step and run again the full release as I had done in previous releases in eg. jupyterlab. There were no 0.4.1. created in the nbclassic repository.
At the end, while monitoring the logs, I have realized that the 0.4.2 was being pushed, and not 0.4.1...
@blink1073 any idea what has happend
This PR update the changelog to reflect the skipped 0.4.1 version.
@Zsailer Further you comment on gitter, we could manually change the changelog on https://github.com/jupyter/nbclassic/releases/tag/v0.4.2 Is it ok to do so?
(*)