This repository has been archived by the owner on Sep 29, 2023. It is now read-only.
ADAL Python 1.0.0 (was Release Candidate 1.0.0rc1) #137
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
yugangw-msft
approved these changes
Apr 18, 2018
rayluo
changed the title
abhidnya13
approved these changes
May 29, 2018
|
|
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.
We are planning for a 1.0.0
rc1release. The following content will become release note:The default value of
api_versionparameter in theAuthenticationContextconstructor will be changed from "1.0" to None. The previous default value "1.0" was a middleground between backward compatibility and new behavior, but it was not very noticeable and people occasionally forgot to opt-in for the new behavior.Now we will enable the new behavior by default. Please test this new behavior, and if you encounter issues, please let us know. And you can also explicitly set it to "1.0" to maintain the old behavior, if needed.
To test this release candidate, you can install it by:
Note to self: Do NOT merge this PR yet. We will keep it for a week or two, so that people can test it. Upon merging, we will also need to: (1) rebase to latest dev; (2) change merge base to master.Done.