Skip to content

Release/3.0.0 #480

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 181 commits into from
Closed

Release/3.0.0 #480

wants to merge 181 commits into from

Conversation

nikithauc
Copy link
Contributor

#444

Changes in this release are added in the 3.0.0 Milestone and
the V3 upgrade guide

cc: @roinochieng

nokafor and others added 30 commits December 29, 2019 13:37
nikithauc and others added 11 commits June 2, 2021 13:44
* Fixing links

* Update v3-upgrade-guide.md
* Adding the ChunkRecord interface

* Adding more tests for stream resume

* comments, assert conditions change

* SliceRecord and comments
* 3.0.0 preview 2 package update

* restore file
* adding links to samples

* removing duplicate links

* adding description for typings and removing en-us
* removing node and browser; adding largefile samples

* adding links of samples in docs

* token credential readme change
* @returns The sliced file part
*/
public async sliceFile(range: Range): Promise<SliceType> {
let rangeSize = range.maxValue - range.minValue + 1;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

defensive programing on range

MIchaelMainer
MIchaelMainer previously approved these changes Jul 9, 2021
Copy link
Contributor

@MIchaelMainer MIchaelMainer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vincent caught some valid issues. Since none of these are release blockers, let's open tracking issues to be addressed in 3.0.1 release which can be done next week. Please open tracking issues and provide links in your response to Vincent.

@nikithauc nikithauc mentioned this pull request Jul 10, 2021
@baywet
Copy link
Member

baywet commented Jul 12, 2021

@MIchaelMainer my main concern here is this

This library is no longer receiving new features and will only receive critical bug and security fixes. All new applications should use @azure/msal-browser instead.

from https://www.npmjs.com/package/msal

And I think we should seriously review upgrading to the newer package instead of releasing something with a dependency on a deprecated package.

@nikithauc
Copy link
Contributor Author

nikithauc commented Jul 12, 2021

@baywet msal-browser authprovider is a feature for 3.1.0.
3.1 Milestone
Feature request will deal with msal auth libraries and more work on our auth story.

ImplicitMsalAuthenticationProvider for msal 1.0.0 is deprecated so that we give some time for the users to move to the newer auth library. The deprecation of the ImplicitMsalAuthenticationProvider has been mentioned in the code and upcoming blogpost.
As the name suggests, the ImplicitMsalAuthenticationProvider is for the Implicit Auth flow and cannot directly take a dependency on Msal 2.0.0.

ImplicitMsalAuthenticationProvider is an existing feature that is being deprecated. We are not adding taking a new dependency to msal in this release.

@baywet
Copy link
Member

baywet commented Jul 12, 2021

@nikithauc thanks for the additional information. Is the plan to remove the implicit provider when adding support for msal browser (and removing msal from the deps) ?

@nikithauc
Copy link
Contributor Author

@nikithauc thanks for the additional information. Is the plan to remove the implicit provider when adding support for msal browser (and removing msal from the deps) ?

@baywet I will have to check on that and get back. The discussion on when to remove is yet to happen.

@baywet
Copy link
Member

baywet commented Jul 12, 2021

@nikithauc to expand a little bit: removing something, even if it was marked as deprecated before, should be considered a breaking change. In this case, if we decide to keep the implicit flow provider for v3, it means we can only remove it with v4 if we want to avoid breaking people according to semver. This is why I was surprised to see it was still here given the fact the flow has been deprecated for a while now, it forces us to keep a dependency on a deprecated package, and it'll force a new major version.
I do think we should consider removing it now to alleviate all those concerns.

@nikithauc
Copy link
Contributor Author

@nikithauc to expand a little bit: removing something, even if it was marked as deprecated before, should be considered a breaking change. In this case, if we decide to keep the implicit flow provider for v3, it means we can only remove it with v4 if we want to avoid breaking people according to semver. This is why I was surprised to see it was still here given the fact the flow has been deprecated for a while now, it forces us to keep a dependency on a deprecated package, and it'll force a new major version.
I do think we should consider removing it now to alleviate all those concerns.

@baywet I would like to deprecate this now as discussed and remove it in v4.0.
We will be having the custom msal auth providers in 3.1.0. This helps in providing the users more alternatives to migrate to newer auth libraries easily when we remove the ImplicitMsalAuthenticationProvider and they decide to move from Implicit Auth Flow.

cc: @ddyett

@nikithauc
Copy link
Contributor Author

@baywet I have updated the node requirement as I felt that would be relevant for this release. Thanks for pointing that out!

The other enhancement changes will be addressed in other PRs.

@nikithauc nikithauc closed this Aug 2, 2021
@nikithauc nikithauc deleted the release/3.0.0 branch August 2, 2021 18:11
@nikithauc nikithauc mentioned this pull request Aug 2, 2021
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.

8 participants