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.
Some changes in jupyter_telemetry are pending that will lead to breaking changes here in jupyterhub. jupyter_telemetry is likely going to require event schemas to explicitly state if+when they are collecting personal data. This is critically important for protecting user's personal data. Once these changes land in jupyter_telemetry, JupyterHub's event schemas will need updating to include the new, required fields.
In the meantime, I think it's wise for jupyterhub to pin its dependency to the current release of jupyter_telemetry so we don't have to coordinate a release of jupyter_telemetry and jupyterhub w/ new event schemas.
I'll update JupyterHub's event schemas once jupyter/telemetry#46 merges and jupyter_telemetry has a new release.