Skip to content

Conversation

@rayluo
Copy link
Contributor

@rayluo rayluo commented Jun 17, 2019

Each of the sub-PRs included in this release has been tested and reviewed and approved in their individual PR. The purpose of this all-in-one release PR is to organize the release process. Please review/proof-read the following release notes.

Release Notes:

If you prefer to, you can install this branch for your smoke testing:

pip install git+https://github.com/AzureAD/microsoft-authentication-library-for-python.git@release-0.4.1

rayluo and others added 24 commits May 22, 2019 13:27
Updating authority URL regexp to not escape question mark
Handle string time values when caching responses
Previous implementation was largely based on some hallway communication,
which happened to not work in sovereign scenario.
Neither did we test sovereign scenario for MSAL Python, until now.
Bumping version number
@rayluo rayluo requested review from abhidnya13 and henrik-me June 17, 2019 23:35
Jann Roder and others added 3 commits June 18, 2019 09:28
Although not strictly enforced (by pylint) in this repo,
we don't want to noticeably exceed that limit.
https://www.python.org/dev/peps/pep-0008/#maximum-line-length
Pass through verify flag and fix scopes default value
rayluo added 3 commits June 18, 2019 09:28
The previous default None value would cause an exception in our code decorate_scope().
The fix is to change the previously optional scopes parameter to required.
This kind of api surface change would usually be a breaking change, but in this case it is not,
because the previous default value would cause exception so it was in fact required.
FWIW, you can still explicitly use empty list [] as scope,
and the response would contain id_token and refresh_token, but no access_token.
…assword-flow

Change an optional scopes parameter to be required
Bringing 2 more PRs into pending release-0.4.1 branch
@rayluo rayluo merged commit 210103c into master Jun 18, 2019
@rayluo rayluo deleted the release-0.4.1 branch June 18, 2019 18:27
DharshanBJ pushed a commit that referenced this pull request Oct 4, 2024
The red cross i.e. a CI test failure when merging previous PR 61 into dev branch, was a rare intermittent failure in the CI side. In fact, its previous CI test and its subsequent merging into dev branch have all been successful. Therefore we ignore that red cross, and still proceed with our release.

Recording such reasoning here for future reference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants