Skip to content

build: publish-release script should run npm login before build #16188

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

Conversation

devversion
Copy link
Member

Building the release packages can take up a lot of time and we
should rather run npm login before starting the build because
otherwise if the login fails, the output needs to be rebuilt again.

Additionally this commit fixes that existing local/remote tags are
not properly parsed due to an issue with the Git references that
refer to tags.

Closes #16141

Building the release packages can take up a lot of time and we
should rather run `npm login` before starting the build because
otherwise if the login fails, the output needs to be rebuilt again.

Additionally this commit fixes that existing local/remote tags are
not properly parsed due to an issue with the Git references that
refer to tags.

Closes angular#16141
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Jun 3, 2019
@devversion devversion requested a review from jelbourn as a code owner June 3, 2019 10:11
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 3, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jun 6, 2019
@devversion devversion added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Jun 6, 2019
@josephperrott josephperrott merged commit 70aee92 into angular:master Jun 6, 2019
josephperrott pushed a commit that referenced this pull request Jun 10, 2019
Building the release packages can take up a lot of time and we
should rather run `npm login` before starting the build because
otherwise if the login fails, the output needs to be rebuilt again.

Additionally this commit fixes that existing local/remote tags are
not properly parsed due to an issue with the Git references that
refer to tags.

Closes #16141
RudolfFrederiksen pushed a commit to RudolfFrederiksen/material2 that referenced this pull request Jun 21, 2019
…lar#16188)

Building the release packages can take up a lot of time and we
should rather run `npm login` before starting the build because
otherwise if the login fails, the output needs to be rebuilt again.

Additionally this commit fixes that existing local/remote tags are
not properly parsed due to an issue with the Git references that
refer to tags.

Closes angular#16141
@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 Sep 10, 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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move npm login check before building in publish-release
4 participants