-
Notifications
You must be signed in to change notification settings - Fork 221
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: heroku/cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.46.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: heroku/cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.46.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 10 files changed
- 4 contributors
Commits on Oct 20, 2020
-
Add helpful error message for VaaS MFA users
* Soon, we will roll out a beta where users can have MFA/2FA for their Heroku Accounts using VaaS (verification as a service), a Salesforce platform that all clouds are adopting. * In the next few months, we will migrate all existing Heroku 2FA users over to VaaS. The login experience will still be very similar for these users, but they will be verifying themselves via the VaaS redirect interface rather than on the Heroku home-grown 2FA flow. * Users who are migrated over may not even know it, so they may attempt to disable MFA via CLI. While technically we could do some trickery with the VaaS Admin API to make this possible, the intent of VaaS is that users go into the VaaS manage page, which is accessible via the Heroku Dashboard, to do all verifier management. * This CLI command is used very rarely but we figure it doesn't hurt to add a helpful error message here rather than confusingly telling users with VaaS MFA enabled that they do not have 2FA enabled (because they do...it's just a *different* 2FA). * https://gus.my.salesforce.com/a07B0000008TzijIAC
Configuration menu - View commit details
-
Copy full SHA for 49f815c - Browse repository at this point
Copy the full SHA 49f815cView commit details -
Configuration menu - View commit details
-
Copy full SHA for da64ece - Browse repository at this point
Copy the full SHA da64eceView commit details -
Configuration menu - View commit details
-
Copy full SHA for 16950b7 - Browse repository at this point
Copy the full SHA 16950b7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3111384 - Browse repository at this point
Copy the full SHA 3111384View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3b65e5b - Browse repository at this point
Copy the full SHA 3b65e5bView commit details -
Update packages/auth/src/commands/auth/2fa/disable.ts
Co-authored-by: Stanley Stuart <fivetanley@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for b5f9bf6 - Browse repository at this point
Copy the full SHA b5f9bf6View commit details -
Configuration menu - View commit details
-
Copy full SHA for d3c36cb - Browse repository at this point
Copy the full SHA d3c36cbView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v7.46.0...v7.46.1