Upgrade to z2jh 1.2.0 #1079
Merged
Upgrade to z2jh 1.2.0 #1079
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is the latest stable version. We want to eventually move to 2.0 (with some breaking changes) but let's get to the latest non 2.0 stable version first Ref 2i2c-org#1055
consideRatio
approved these changes
Mar 10, 2022
GeorgianaElena
approved these changes
Mar 10, 2022
choldgraf
approved these changes
Mar 10, 2022
|
Looked at the very nicely maintained changelog here: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/main/CHANGELOG.md#120---2021-11-04. Seems good :) I'm testing this on staging, and then deploying after. |
|
When upgrading z2jh, it is important to check if there is anything we need to check in the images used for it to work with the new version of z2jh. 1.1.x to 1.2.x doesn't have any such changes though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the latest stable version. We want to eventually
move to 2.0 (with some breaking changes) but let's get to
the latest non 2.0 stable version first
Ref #1055