MSAL Go 0.9.0

[rayluo]

(The following content will become release notes.)

This release contains breaking changes. Please refer to "API changes for GA release" for upgrade guidance. (This resolves #380)

• Delete vestigial option function types (Delete vestigial option function types #383)
• Rename public client CreateAuthCodeURL -> AuthCodeURL ([Documentation] CreateAuthCodeURL Naming Consistency #371, Rename public client CreateAuthCodeURL -> AuthCodeURL #384)
• Delete deprecated confidential.NewCredFromAssertion (Delete deprecated confidential.NewCredFromAssertion #385)
• Rename confidential.WithAccessor to WithCache (Rename confidential.WithAccessor to WithCache #386)
• Review all logs to ensure there is no PII (Review logging #28, Logging audit and logging docs #382)
• Upgrade dependencies (Upgrade dependencies #387)
• Remove unused confidential client UserID (Remove unused confidential client UserID #389)
• Replace NewCredFromCert with NewCredFromCertChain (Replace NewCredFromCert with NewCredFromCertChain #391)
• Remove unnecessary options structs (Remove unnecessary options structs #390)
• Upgrade CI tools (Upgrade CI tools #392)
• Adding ExportReplace to support the Context object (Adding ExportReplace to support the Context object [breaking change for 1.0] #378)
• Add optional metadata for cache.ExportReplace (Add optional metadata for cache.ExportReplace #395, [Feature Request] Cache interface is not extensible  #381)
• Confidential client requires authority (Confidential client requires authority #394, Require a specific tenant for confidential clients #348)

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
1.7% Duplication

[bgavrilMS]

LGTM

Should we call this 1.0.0-preview instead of 0.9.0 ?

[rayluo]

LGTM

Should we call this 1.0.0-preview instead of 0.9.0 ?

This 0.9.0 turns out to be a 1.0.0-preview, which happens to be a tradition of MSAL Python's 0.9 and 1.0 (this time, we will leave some meaningful buffer between the two's releases, though). :-)

[Yesterday 10:16 AM] Charles Lowell
I'm thinking ... v0.9.0 will be a release candidate with the 1.0 API. That makes the last 0.x compatible with 1.0, gives customers some time to upgrade, and gives us ... time to complete reviews or whatever other compliance work is necessary before 1.0