Tooling Monorepo #49

JoshuaBatty · 2025-10-29T04:30:17Z

Note

Adds an RFC proposing a new forc-tooling monorepo for operational tooling and CLI wrappers, keeping AST-aware binaries in Sway, with defined migration, distribution, CI, and release processes.

RFC Added: rfcs/0017-tooling-monorepo.md introducing a split into a new forc-tooling monorepo.
- Scope:
  - Move CLI wrappers (forc-fmt, forc-lsp, forc-doc, forc-migrate) and operational tools (forc-node, forc-client, forc-crypto, forc-wallet) to forc-tooling.
  - Keep AST-aware implementations (swayfmt, sway-lsp, sway-doc, sway-migrate) in sway.
- Distribution: Update sway-nightly-binaries, fuelup, and fuel.nix to source binaries from both repos.
- CI & Compatibility: Separate CI pipelines; track cross-repo compatibility via compatibility.toml.
- Release Pipeline: Independent crate releases from forc-tooling; atomic installs via dual manifests.
- Implementation Plan: Bootstrap repo, migrate tools, introduce wrapper crates, update distribution, rollout/monitor.
- Release Tooling Options: Consider release-plz, cargo-smart-release, cargo-unleash.
- Notes: Drawbacks, alternatives, prior art, and unresolved questions documented.

^{Written by Cursor Bugbot for commit 9f0d425. This will update automatically on new commits. Configure here.}

… RFC 0017.

kayagokalp

This looks great to me! Only thing we might want to clarify/discuss is versioning as the binary that invoking compiler capabilities now will be decoupled from the sway repo.

As RFC discusses with the ability to version different packages independently, we should be able to continue following those version sets (like forc-fmt is actually at the same level as the compiler releases) while keeping rest of the tools like forc-client independent from these bumps.

I think we can also revive a simplified version of "releasy" which is going to actually just watch for releases in sway repo and open bump PRs on the tooling monorepo (like sway-core bumped on sway side etc). This can be useful for situations like getting latest language features released into forc-fmt semi-automatically, as there will be a PR already.

I am curios whether we consider forc as a tooling monorepo thing or sway monorepo thing? I feel like it should be tooling monorepo while its sway repo dependency is forc-pkg but without an automatic process described as above, language releases will require an additional PR merged. It is not the end of the world but something to consider

xunilrj · 2025-11-10T23:17:34Z

rfcs/0017-tooling-monorepo.md

+| **Sway**         | Compiler, language services, AST-aware binaries | Publishes `swayfmt`, `sway-lsp`, `sway-doc`, `sway-migrate` , and related libraries consumed by tooling wrappers                 |
+| **Forc-tooling** | CLI wrappers and operational tools              | Hosts `forc-fmt`, `forc-lsp`, `forc-doc`, `forc-node`, `forc-client`, `forc-crypto`, `forc-wallet`, and tracing/deploy utilities |
+
+Both repos maintain independent CI pipelines:


It would be interesting to allow sway CI to trigger some upstream tests. The new tooling repo is one of them.

In this way, we would know that something is breaking. This CI task would not block merge, but would signal to someone else that changes are coming.

cursor · 2025-12-02T08:59:15Z

PR Summary

Adds an RFC proposing a separate forc-tooling monorepo, keeping AST-aware binaries in sway, with defined CI, release, and compatibility tracking.

RFC Added: rfcs/0017-tooling-monorepo.md
- Proposes creating a dedicated forc-tooling monorepo for CLI wrappers and operational tools while keeping swayfmt, sway-lsp, sway-doc, sway-migrate in sway.
- Repository boundaries:
  - sway: compiler, language services, AST-aware binaries
  - forc-tooling: forc-fmt, forc-lsp, forc-doc, forc-migrate (wrappers), forc-node, forc-client, forc-crypto, forc-wallet, tracing/deploy tools
- Distribution: update fuelup, fuel.nix, and nightly pipelines to source tooling from the new repo.
- CI/Release: independent pipelines; tooling publishes separately; atomic installs supported.
- Compatibility tracking: auto-generate releases.toml from Cargo.lock per release.
- Implementation plan: bootstrap repo, migrate operational tools, introduce wrappers, adapt distribution, and monitor rollout.
- Tooling options: outlines multi-crate release tools (release-plz, cargo-smart-release, cargo-unleash).
- Notes drawbacks, rationale/alternatives, prior art, and unresolved questions.

^{Written by Cursor Bugbot for commit 60dfcb3. This will update automatically on new commits. Configure here.}

…onorepo with improved dependency management in Cargo.toml files.

Update all channel TOML files to use the new simplified target naming convention for forc-wallet: - aarch64-unknown-linux-gnu → linux_arm64 - x86_64-unknown-linux-gnu → linux_amd64 - aarch64-apple-darwin → darwin_arm64 - x86_64-apple-darwin → darwin_amd64 This aligns with the forc-wallet release asset renaming and the simplified naming convention adopted by the forc monorepo. Note: fuel-core and fuel-core-keygen entries are intentionally unchanged as their release assets have not been renamed. Closes #809 Related: #808 RFC: FuelLabs/sway-rfcs#49

## Summary This PR completes the sway-side of migrating `forc-tracing` and `forc-crypto` to the new [forc monorepo](https://github.com/FuelLabs/forc), as outlined in [RFC #49](FuelLabs/sway-rfcs#49). The corresponding forc repo PR: FuelLabs/forc#119 ### Changes - Remove `forc-tracing` crate from workspace (now uses crates.io `0.71.1`) - Remove `forc-crypto` crate from workspace - Update CI to no longer build/package `forc-crypto` binary (it's now built from forc repo) - Update gh-pages workflow to install `forc-crypto` from forc repo for documentation generation ### Distribution Going forward, `forc-crypto` will be built and distributed from the forc repo by: - sway-nightly-binaries - fuelup - fuel.nix ### Documentation For now, documentation for all tooling will continue to live in this repo. The `gh-pages` workflow now pulls `forc-crypto` from the forc repo rather than building it locally, so docs generation continues to work as before.

Update all channel TOML files to use the new simplified target naming convention for forc-wallet: - aarch64-unknown-linux-gnu → linux_arm64 - x86_64-unknown-linux-gnu → linux_amd64 - aarch64-apple-darwin → darwin_arm64 - x86_64-apple-darwin → darwin_amd64 This aligns with the forc-wallet release asset renaming and the simplified naming convention adopted by the forc monorepo. Note: fuel-core and fuel-core-keygen entries are intentionally unchanged as their release assets have not been renamed. Closes #809 Related: #808 RFC: FuelLabs/sway-rfcs#49

…#811) Update all channel TOML files to use the new simplified target naming convention for forc-wallet: - aarch64-unknown-linux-gnu → linux_arm64 - x86_64-unknown-linux-gnu → linux_amd64 - aarch64-apple-darwin → darwin_arm64 - x86_64-apple-darwin → darwin_amd64 This aligns with the forc-wallet release asset renaming and the simplified naming convention adopted by the forc monorepo. Note: fuel-core and fuel-core-keygen entries are intentionally unchanged as their release assets have not been renamed. Closes #809 Related: #808 RFC: FuelLabs/sway-rfcs#49

## Summary Migrates `forc-node` package support from the `sway` repository to the `forc` monorepo, effective from version 0.71.0 onwards. This follows the same pattern established in #205 for `forc-crypto`. ## Changes - **refresh-manifests.sh**: Added `pkg_forc_node` with legacy repo routing (sway < 0.71.0, forc >= 0.71.0) - **patches.nix**: - Added `forc-node` to `forc-plugins` list for openssl dependencies - Added `buildAndTestSubdir` patch for forc monorepo builds - Added clang/rocksdb dependencies required for fuel-core bindings - **packages.md**: Added forc-node to documentation ## Related PRs - forc: [FuelLabs/forc#130](FuelLabs/forc#130) - Migrate forc-node from sway repo - fuelup: [FuelLabs/fuelup#819](FuelLabs/fuelup#819) - Migrate forc-node from sway to forc monorepo - sway-nightly-binaries: [FuelLabs/sway-nightly-binaries#81](FuelLabs/sway-nightly-binaries#81) - Migrate forc-node nightly builds ## RFC [FuelLabs/sway-rfcs#49](FuelLabs/sway-rfcs#49) - Tooling Monorepo RFC --------- Co-authored-by: GitHub Action <action@github.com>

## Summary This PR completes the sway-side of migrating `forc-node` to the [forc monorepo](https://github.com/FuelLabs/forc), as outlined in [RFC #49](FuelLabs/sway-rfcs#49). The corresponding forc repo PR: FuelLabs/forc#130 `forc-node` has already been released from the forc repo (v0.71.2). ### Changes - Remove `forc-node` crate from workspace - Update CI to no longer build/test/package `forc-node` binary (it's now built from forc repo) - Update gh-pages workflow to install `forc-node` from forc repo for documentation generation - Remove unused workspace dependencies (`fuel-core`, `fuel-core-chain-config`, `libp2p-identity`, `sha1`, `termion`) ### Distribution Going forward, `forc-node` will be built and distributed from the forc repo by: - sway-nightly-binaries - fuelup - fuel.nix ### Documentation Documentation for all tooling will continue to live in this repo. The `gh-pages` workflow now pulls `forc-node` from the forc repo rather than building it locally, so docs generation continues to work as before. Co-authored-by: Igor Rončević <ironcev@hotmail.com>

add init commit for tooling monorepo rfc

4bee1ca

JoshuaBatty force-pushed the josh/tooling branch from 73511cf to 4bee1ca Compare October 29, 2025 04:31

JoshuaBatty self-assigned this Oct 29, 2025

Add multi-crate release tooling section and related considerations to…

4866812

… RFC 0017.

This comment was marked as outdated.

Sign in to view

update

4ae58a5

JoshuaBatty changed the title ~~[WIP] Tooling Monorepo~~ Tooling Monorepo Nov 6, 2025

update Implementation Plan

9f0d425

kayagokalp approved these changes Nov 6, 2025

View reviewed changes

JoshuaBatty requested review from a team, Voxelot, mchristopher and zees-dev November 7, 2025 00:28

xunilrj reviewed Nov 10, 2025

View reviewed changes

JoshuaBatty mentioned this pull request Nov 12, 2025

feat: migrate forc-wallet repository to forc monorepo FuelLabs/forc#1

Merged

8 tasks

JoshuaBatty mentioned this pull request Nov 21, 2025

feat: enable forc-wallet migration from standalone repo to forc monorepo FuelLabs/fuelup#807

Merged

JoshuaBatty mentioned this pull request Nov 30, 2025

feat: migrate forc-wallet nightly builds to forc monorepo FuelLabs/sway-nightly-binaries#76

Merged

add Compatibility Tracking section

eecb8ee

Refine compatibility tracking and release documentation for tooling m…

60dfcb3

…onorepo with improved dependency management in Cargo.toml files.

JoshuaBatty mentioned this pull request Dec 10, 2025

feat: use simplified target names for forc-wallet and forc-crypto releases FuelLabs/sway-nightly-binaries#80

Merged

2 tasks

This was referenced Jan 5, 2026

Migrate forc-node from the sway repo FuelLabs/forc#130

Merged

feat: migrate forc-node nightly builds to forc monorepo FuelLabs/sway-nightly-binaries#81

Merged

This was referenced Jan 13, 2026

feat: migrate forc-node from sway to forc monorepo FuelLabs/fuelup#819

Merged

feat: migrate forc-node to forc monorepo FuelLabs/fuel.nix#208

Merged

JoshuaBatty mentioned this pull request Jan 16, 2026

Migrate forc-node to forc monorepo FuelLabs/sway#7534

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Tooling Monorepo #49

Tooling Monorepo #49

Uh oh!

JoshuaBatty commented Oct 29, 2025 •

edited

Loading

Uh oh!

This comment was marked as outdated.

Uh oh!

kayagokalp left a comment •

edited

Loading

Uh oh!

xunilrj Nov 10, 2025

Uh oh!

cursor bot commented Dec 2, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Tooling Monorepo #49

Are you sure you want to change the base?

Tooling Monorepo #49

Uh oh!

Conversation

JoshuaBatty commented Oct 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment was marked as outdated.

Uh oh!

kayagokalp left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

xunilrj Nov 10, 2025

Choose a reason for hiding this comment

Uh oh!

cursor bot commented Dec 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

JoshuaBatty commented Oct 29, 2025 •

edited

Loading

kayagokalp left a comment •

edited

Loading

cursor bot commented Dec 2, 2025 •

edited

Loading