Optical Disc 💿
Optical Disc 💿•7mo ago

Unable to build crate with deno_runtime 0.139.0 or 0.140.0, due to version numbering in deno_ast

The two most recently released versions of the deno_runtime crate cannot build at all, due to its build dependency deno_ast ^1.0.1. The latest version of deno_ast is 0.32.1, but cargo reads that as a lower version number, and therefore refuses to use it. The exact version 1.0.1 of deno_ast was yanked from crates.io, so it can't be used for building.
3 Replies
Optical Disc 💿
Optical Disc 💿•7mo ago
$ cargo build # Attempt with deno_runtime = "0.139.0"
    Updating crates.io index
error: failed to select a version for the requirement `deno_ast = "^1.0.1"`
candidate versions found which didn't match: 0.32.1, 0.32.0, 0.31.6, ...
location searched: crates.io index
required by package `deno_runtime v0.139.0`
    ... which satisfies dependency `deno_runtime = "^0.139.0"` of package `<crate-name> v0.1.0 (/var/home/opticaldisc/<path>)`
perhaps a crate was updated and forgotten to be re-vendored?
$ cargo build # Attempt with deno_runtime = "0.139.0"
    Updating crates.io index
error: failed to select a version for the requirement `deno_ast = "^1.0.1"`
candidate versions found which didn't match: 0.32.1, 0.32.0, 0.31.6, ...
location searched: crates.io index
required by package `deno_runtime v0.139.0`
    ... which satisfies dependency `deno_runtime = "^0.139.0"` of package `<crate-name> v0.1.0 (/var/home/opticaldisc/<path>)`
perhaps a crate was updated and forgotten to be re-vendored?
$ cargo build # Attempt with deno_runtime = "0.140.0"
    Updating crates.io index
error: failed to select a version for the requirement `deno_ast = "^1.0.1"`
candidate versions found which didn't match: 0.32.1, 0.32.0, 0.31.6, ...
location searched: crates.io index
required by package `deno_runtime v0.140.0`
    ... which satisfies dependency `deno_runtime = "^0.140.0"` of package `<crate-name> v0.1.0 (/var/home/opticaldisc/<path>)`
perhaps a crate was updated and forgotten to be re-vendored?
$ cargo build # Attempt with deno_runtime = "0.140.0"
    Updating crates.io index
error: failed to select a version for the requirement `deno_ast = "^1.0.1"`
candidate versions found which didn't match: 0.32.1, 0.32.0, 0.31.6, ...
location searched: crates.io index
required by package `deno_runtime v0.140.0`
    ... which satisfies dependency `deno_runtime = "^0.140.0"` of package `<crate-name> v0.1.0 (/var/home/opticaldisc/<path>)`
perhaps a crate was updated and forgotten to be re-vendored?
Deno AI Helper
Deno AI Helper•7mo ago
I wasn't able to find the answer to your question in the official Deno documentation. However, based on the information you've provided, it seems like there might be a versioning issue with the deno_ast crate that is causing the build process to fail. The deno_runtime crate you are trying to build has a dependency on deno_ast with a version specification of ^1.0.1. However, if the version 1.0.1 has been yanked and the latest version is 0.32.1, Cargo will indeed see 0.32.1 as a lower version and not compatible with the specified ^1.0.1 requirement. This advice is not based on the Deno documentation, so please double-check the accuracy of this advice. You might want to check the release notes or updates from the Deno team regarding this issue, or reach out to the maintainers of the deno_runtime crate for guidance on how to proceed with the build or if there is a workaround or fix available.
Helpful Links: Deno 1.7 Release Notes Deno 1.36: More flexible security and expanded testing APIs Deno 1.28: Featuring 1.3 Million New Modules Deno 1.32: Enhanced Node.js Compatibility
bartlomieju
bartlomieju•7mo ago
More Posts
walk() include only last directory...Hey, I'm currently trying to write a replacer for file names, file content and folder names. My goalHow to link local NPM package with DenoI have a package which has a couple of peer dependencies, which I want to link locally and patch. WhSubhosting API protectionIs there a way to setup custom auth via some header for example for all subhosting routes? I.e. Denolvim tsx language serverafter i clone fresh example in deno deploy, I get an error "Cannot find name 'React' " while openingHow to debug tests in Deno on VSCODEHello everyone, I am trying to debug a unit test in Deno. I have tried using deno test --inspect-brkDynamically importing NPM modules errorsThe following works fine in Node: ```js const parser = 'acorn'; const { parse } = await import(parsedeno kv watch vs broadcast channelFor creating a chat app for example, which one should i use? What are the differences? Kv watch geIf I use FFI with Deno Jupyter, will it not print the shared lib's stdout? (like Rust println!())If I use FFI with Deno Jupyter, will it not print the shared lib's stdout? This is an example of h