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.
Is there something else to include before going for a 2.0.0b1 release?
I've recently self-merged these and included them in this changelog.
Link to rendered changelog: https://the-littlest-jupyterhub--1000.org.readthedocs.build/en/1000/reference/changelog.html
I've not done work including v1 -> v2 upgrade instructions. My take is that its relevant to do when there is a distribution specific migration that needs to be done for example, but I think that isn't the case for this major version of tljh, so I've leaned on referencing other software's changelogs.