Skip to content

build: add otp prompt to release tool #17035

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

Merged
merged 1 commit into from
Sep 10, 2019

Conversation

jelbourn
Copy link
Member

No description provided.

@jelbourn jelbourn added pr: merge safe target: minor This PR is targeted for the next minor release labels Sep 10, 2019
@jelbourn jelbourn requested a review from devversion September 10, 2019 17:15
@jelbourn jelbourn requested a review from a team as a code owner September 10, 2019 17:15
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 10, 2019
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

LGTM 💯

@devversion devversion added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Sep 10, 2019
@@ -123,8 +123,12 @@ class PublishReleaseTask extends BaseReleaseTask {
// the user to interactively confirm that the script should continue.
await this._promptConfirmReleasePublish();

// Prompt for the OTP right before publishing so that it doesn't expire while building the
// packages.
const npmOtp = await promptForNpmOtp();
Copy link
Member

Choose a reason for hiding this comment

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

Optional: just something I noticed after approving. Maybe we should have a comment here saying that the OTP token is needed as NPM requires two-factor auth for each write to the registry.

@jelbourn jelbourn merged commit f6564cd into angular:master Sep 10, 2019
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants