| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Of note, @gimli01 is looking into why this automation has a larger diff then @lpinca's PR; As noted in #38828 (comment), this PR was generated via a GitHub Action that will be kicked off immediately after our releases going forward (ref. https://github.com/npm/cli/blob/latest/.github/workflows/create-cli-deps-pr.yml) |
Sorry, something went wrong.
|
Maybe it need sync with latest master? I saw This branch is 1 commit ahead, 1359 commits behind nodejs:master. in https://github.com/npm/node/tree/npm-7.15.0 |
Sorry, something went wrong.
|
There is a no-bot but our bots policy in Node.js's repos:
Does @npm-robot fits in the authorized category? Would it be possible to link to an issue where its introduction has been discussed? |
Sorry, something went wrong.
Hi @aduh95 thank you so much for bringing that up, personally I wasn't aware of the existence of that policy when I first discussed the npm-robot PR strategy but I can totally see the reason for having it 😊 That said, my personal interpretation of the policy is that it's in place to avoid spamming and other unwanted behavior. That wouldn't be the case here. This robot is clearly performing a legitimate task, helping us better integrate npm cli releases timely into node releases.
Could you please help us bring the subject to a future TSC meeting agenda? Given that we have that policy in place I believe the best way to move forward is to make sure get an explicit approval. 🙏 |
Sorry, something went wrong.
|
actually, let me create an issue instead and close this PR as I want to make sure we clean things up in the update npm side of things 😊 Opened: #38879 so that we can continue the conversation there. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
v7.15.0 (2021-05-27)
FEATURES
BUG FIXES
DOCUMENTATION
DEPENDENCIES
AUTOMATION