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.

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

fix: canonical vm adjustments #544

Merged
merged 14 commits into from
Sep 30, 2022
Merged

fix: canonical vm adjustments #544

merged 14 commits into from
Sep 30, 2022

Conversation

lgalabru
Copy link
Contributor

The current develop is now pulling the canonical (non wasm compatible, yet) vm, which Is breaking the new wasm lsp.
With this branch, we're adding some tweaks to the dependency graph, making it so wasm builds depends on the latest wasm compatible repl deployed on crates.io.

Ludo Galabru and others added 4 commits September 23, 2022 15:06
# Conflicts:
#	Cargo.lock
#	components/clarinet-deployments/src/lib.rs
#	components/clarinet-deployments/src/requirements.rs
#	components/clarinet-deployments/src/types.rs
#	components/clarinet-files/src/network_manifest.rs
#	components/clarity-lsp/src/common/backend.rs
#	components/clarity-lsp/src/common/state.rs
#	components/clarity-lsp/src/utils/mod.rs
@lgalabru lgalabru enabled auto-merge September 26, 2022 16:11
@lgalabru lgalabru self-assigned this Sep 26, 2022
@lgalabru lgalabru changed the title fix: wasm-lsp should target published v0.33.0 fix: canonical vm adjustment Sep 29, 2022
@lgalabru lgalabru changed the title fix: canonical vm adjustment fix: canonical vm adjustments Sep 29, 2022
@lgalabru lgalabru disabled auto-merge September 30, 2022 17:16
@lgalabru lgalabru merged commit 3cdc869 into develop Sep 30, 2022
@lgalabru lgalabru deleted the fix/lsp-repl-wasm branch September 30, 2022 17:55
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.

1 participant