Skip to content

fix(js-runtimes): make the crate its own workspace root #1299

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

Merged
hyperpolymath merged 2 commits into from
Oct 19, 2026
Merged

fix(js-runtimes): make the crate its own workspace root #1299

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4a6e59f
fix(js-runtimes): make the crate its own workspace root
claude Oct 19, 2026
a805e66
Merge branch 'main' into claude/js-runtimes-own-workspace
hyperpolymath Oct 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions tools/js-runtimes/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,3 +20,11 @@ path = "src/main.rs"
# I-JSON (RFC 7493) + JCS (RFC 8785), in-process (owner ruling D306).
# Pinned by commit: ijson-jcs has no releases yet.
ijson-jcs = { git = "https://github.com/hyperpolymath/ijson-jcs", rev = "3a9a4ee326a968a32b2f152b4faec243a2d00765" }

# Its own workspace root, on purpose. The governance and js-runtimes
# reusables check this crate out at .standards-js/ INSIDE the caller's
# checkout and `cargo install --path` it from there. In a caller whose root
# Cargo.toml is a workspace, cargo would otherwise take this crate for an
# undeclared member and refuse to build it ("current package believes it's
# in a workspace when it's not"). Hit by hyperpolymath/hypatia#929.
[workspace]
Loading