Backport PR #6949 on branch 1.0.x (Fix comm_info_request content to conform to spec in a backwards-compatible way) #6958
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
… to spec in a backwards-compatible way
|
Thanks for making a pull request to JupyterLab! To try out this branch on binder, follow this link: |
|
@saulshanabrook, does our Azure Pipeline only run on certain branches? |
|
meeseeks should have added the 1.0.x milestone, not the 1.1 milestone. |
|
(of course, there was no 1.0.x milestone - but why did it add 1.1?) |
lock
bot
added
the
status:resolved-locked
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport PR #6949: Fix comm_info_request content to conform to spec in a backwards-compatible way