Repository navigation
feat: upgrade Hub and Lab to JupyterHub 6.0.1 - #35
Merged
Merged
Conversation
Delemangi
marked this pull request as ready for review
October 10, 2026 15:07
This file contains hidden or 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
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.
Scope
Upgrade Hub and Lab to JupyterHub 6.0.1 with matching lockfile resolutions and required transitive dependency updates. Hub retains its supported-range constraint style (
>=6.0,<6.1); Lab retains its exact pin (==6.0.1). Keep focused Web Hub API compatibility tests.This cleanup removes the custom image overrides, database-upgrade switch and culler-mode changes, rollout guards, updater policy changes, standalone workflow and maintenance documentation. Baseline deployment configuration, updater behavior and existing organization reusable CI are retained; no new deployment framework is introduced.
Validation
Local lock, Ruff/format, Hub settings tests (13), Web API tests (8) and Web TypeScript checks passed. Windows cannot validate the POSIX-dependent Hub/Lab suites and type checks; native Linux CI remains required.
Historical validation run 38138838188 exercised the pre-cleanup candidate only. It is not evidence for this cleanup, current runtime or migration behavior. Upstream database-schema migration remains a deployment consideration; no current migration rehearsal or production validation is claimed. No merge or deployment is authorized.