Skip to content
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.

Sign up for GitHub

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

Jump to bottom

deno_fetch forces reqwest =0.11.20 #403

Open
rscarson opened this issue Jan 1, 2024 · 5 comments
Open

deno_fetch forces reqwest =0.11.20 #403

rscarson opened this issue Jan 1, 2024 · 5 comments
Assignees
@littledivy

Comments

@rscarson
Copy link
Contributor

rscarson commented Jan 1, 2024 •
edited

Happened somewhere between v0.150.0 and 0.153.0
@rscarson rscarson changed the title deno_web forces reqwest =0.11.20 deno_fetch forces reqwest =0.11.20 Jan 1, 2024
@bartlomieju
Copy link
Member

So it appears this was done because of seanmonstar/reqwest#1955. @littledivy did you make a relevant PR to reqwest so we could unpin the dependency?

@littledivy
Copy link
Member

Upstream PR: seanmonstar/reqwest#2080

@wyatt-herkamp
Copy link

So seanmonstar/reqwest#2185 was merged for v0.12.0
I tried updating deno reqwest to v0.12.0. However, this creates a ton of conflicting version issues. Because Reqwest requires Hyper and Http to be v1.

@bartlomieju
Copy link
Member

@littledivy is this issue still relevant to deno_core? Looking at Cargo.lock we don't have any usages of reqwest.

@wyatt-herkamp
Copy link

Here, I made a new issue in the relevant Repository. denoland/deno#23370

As deno_fetch is in deno_runtime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@littledivy littledivy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rscarson @wyatt-herkamp @bartlomieju @littledivy