Skip to content

Conversation

devversion
Copy link
Member

We recently updated to rules_nodejs 3.5.0. This contained a fix
for something we recently tried to achieve using a postinstall
patch. The PR that updated to 3.5.0 became a little out-of-date
due to the PR introducing the postinstall patch being merged, so
that the failure only surfaced when the update PR got merged.

@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels May 19, 2021
@devversion devversion requested a review from a team as a code owner May 19, 2021 17:06
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 19, 2021
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

We recently updated to `rules_nodejs` 3.5.0. This contained a fix
for something we recently tried to achieve using a postinstall
patch. The PR that updated to 3.5.0 became a little out-of-date
due to the PR introducing the postinstall patch being merged, so
that the failure only surfaced when the update PR got merged.
@devversion devversion force-pushed the build/fix-ci-postinstall-patc branch from a98d7a5 to 4e22688 Compare May 19, 2021 17:08
@andrewseguin andrewseguin added the action: merge The PR is ready for merge by the caretaker label May 19, 2021
@andrewseguin andrewseguin merged commit 9d87461 into angular:master May 19, 2021
andrewseguin pushed a commit that referenced this pull request May 19, 2021
We recently updated to `rules_nodejs` 3.5.0. This contained a fix
for something we recently tried to achieve using a postinstall
patch. The PR that updated to 3.5.0 became a little out-of-date
due to the PR introducing the postinstall patch being merged, so
that the failure only surfaced when the update PR got merged.

(cherry picked from commit 9d87461)
@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 Jun 19, 2021
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: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants