release 17.3.0 #781
Merged
release 17.3.0 #781
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
consideRatio
approved these changes
Dec 11, 2024
|
Going foe 17.3.0 seems fine to me! |
|
Thanks! Published 17.3.0 |
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.
only has #780 which proved necessary for refresh_user to not cause problems in our jupyter-health 2i2c deployment where we were testing this. With this, it's been working great.
As I mentioned there, I'm okay with yanking 17.2 and doing a beta here to give refresh_user more testing time, or just make this release and keep moving. Both work for me. I suspect the problem caused by refresh_user for 2i2c is rare (automatic creation of users not recognized by the Authenticator), but it may not be the only one.