Skip to content

manually run dependabot for caniuse-lite #2086

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
Jan 4, 2020

Conversation

alsuren
Copy link
Contributor

@alsuren alsuren commented Jan 3, 2020

It looks like dependabot is able to make a minimal incision and update
caniuse-lite without messing around with the rest of the package lock.
I suspect that dependabot will eventually get around to updating
caniuse-lite if we wait long enough, but I was curious to see how hard
it is to run manually, so I had a go. Turns out it's really easy, but
takes quite a long time.

Steps to reproduce:

Fixes #1914

It looks like dependabot is able to make a minimal incision and update
caniuse-lite without messing around with the rest of the package lock.
I suspect that dependabot will eventually get around to updating
caniuse-lite if we wait long enough, but I was curious to see how hard
it is to run manually, so I had a go. Turns out it's really easy, but
takes quite a long time.

Steps to reproduce:

* clone https://github.com/dependabot/dependabot-core
* docker pull dependabot/dependabot-core
* bin/docker-dev-shell
  * bin/dry-run.rb --dep caniuse-lite npm_and_yarn rust-lang/crates.io
* paste the printed patch into a file (e.g. patchfile.txt)
* patch package-lock.json patchfile.txt
* npm ci && npm start

Fixes rust-lang#1914
@rust-highfive
Copy link

r? @jtgeibel

(rust_highfive has picked a reviewer for you, use r? to override)

@jtgeibel
Copy link
Member

jtgeibel commented Jan 4, 2020

Awesome, thanks for the fix and detailed instructions!

@bors r+

@bors
Copy link
Contributor

bors commented Jan 4, 2020

📌 Commit 808fe7a has been approved by jtgeibel

bors added a commit that referenced this pull request Jan 4, 2020
manually run dependabot for caniuse-lite

It looks like dependabot is able to make a minimal incision and update
caniuse-lite without messing around with the rest of the package lock.
I suspect that dependabot will eventually get around to updating
caniuse-lite if we wait long enough, but I was curious to see how hard
it is to run manually, so I had a go. Turns out it's really easy, but
takes quite a long time.

Steps to reproduce:

* clone https://github.com/dependabot/dependabot-core
* docker pull dependabot/dependabot-core
* bin/docker-dev-shell
  * bin/dry-run.rb --dep caniuse-lite npm_and_yarn rust-lang/crates.io
* paste the printed patch into a file (e.g. patchfile.txt)
* patch package-lock.json patchfile.txt
* npm ci && npm start

Fixes #1914
@bors
Copy link
Contributor

bors commented Jan 4, 2020

⌛ Testing commit 808fe7a with merge e218804...

@bors
Copy link
Contributor

bors commented Jan 4, 2020

☀️ Test successful - checks-travis
Approved by: jtgeibel
Pushing e218804 to master...

@bors bors merged commit 808fe7a into rust-lang:master Jan 4, 2020
@Turbo87
Copy link
Member

Turbo87 commented Jan 4, 2020

@alsuren I'm curious, do you know what dependabot runs to perform this update? does it run some special npm command under the hood that does it?

@alsuren
Copy link
Contributor Author

alsuren commented Jan 5, 2020

I think it recursively deletes the dep from the lockfile and then runs npm install in this case. It has a bunch of different strategies, and calls npm via the JS API, so I might be misinterpreting things.

@Turbo87
Copy link
Member

Turbo87 commented Jan 5, 2020

I see, thanks. would be nice if npm had a builtin command for that like yarn has. or maybe we should switch back to yarn 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get rid of Browserslist: caniuse-lite is outdated. Please run next command npm update warning
5 participants