feat: migrate forc-node to forc monorepo#208
Merged
Merged
Conversation
Migrate forc-node from sway repo to forc monorepo, following the same pattern as forc-crypto (PR #205): - Versions < 0.71.0 source from sway with v{version} tags - Versions >= 0.71.0 source from forc with forc-node-{version} tags Adds clang/rocksdb dependencies required for fuel-core bindings.
PR SummaryMigrates
Written by Cursor Bugbot for commit d4bb6f3. This will update automatically on new commits. Configure here. |
kayagokalp
approved these changes
Jan 14, 2026
JoshuaBatty
added a commit
that referenced
this pull request
Jan 15, 2026
forc-node cannot be built in the Nix sandbox due to two blocking issues: - #196: fuel-core-wasm-executor requires network access during build - #209: ethers-contract abigen! macro cannot find ethers crate This keeps the migration changes from #208 (routing forc-node to forc repo for versions >= 0.71.0) but disables the package until both issues are resolved.
JoshuaBatty
added a commit
that referenced
this pull request
Jan 15, 2026
forc-node cannot be built in the Nix sandbox due to two blocking issues: - #196: fuel-core-wasm-executor requires network access during build - #209: ethers-contract abigen! macro cannot find ethers crate This keeps the migration changes from #208 (routing forc-node to forc repo for versions >= 0.71.0) but disables the package until both issues are resolved. Also fixes book.toml for mdbook 0.5.1 compatibility (removes deprecated `multilingual` field introduced by flake.lock update in #208).
JoshuaBatty
added a commit
that referenced
this pull request
Jan 15, 2026
## Summary Temporarily disables `forc-node` packaging until two blocking issues are resolved: - #196: `fuel-core-wasm-executor` requires network access during build (cargo install in build.rs) - #209: `ethers-contract` abigen! macro cannot find ethers crate in Nix sandbox ## Changes - Added filter in `filters.nix` to exclude all forc-node packages - Removed forc-node manifest files (they will be regenerated when re-enabled) ## Context PR #208 was merged adding forc-node support, but the package cannot actually build in the Nix sandbox due to the above issues. This PR keeps the migration infrastructure (routing to forc repo for >= 0.71.0) but disables the package until the blocking issues are resolved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Migrates
forc-nodepackage support from theswayrepository to theforcmonorepo, effective from version 0.71.0 onwards.This follows the same pattern established in #205 for
forc-crypto.Changes
pkg_forc_nodewith legacy repo routing (sway < 0.71.0, forc >= 0.71.0)forc-nodetoforc-pluginslist for openssl dependenciesbuildAndTestSubdirpatch for forc monorepo buildsRelated PRs
RFC
FuelLabs/sway-rfcs#49 - Tooling Monorepo RFC