feat: migrate forc-crypto from sway to forc monorepo

[JoshuaBatty]

Summary

This PR enables fuelup to source forc-crypto from the FuelLabs/forc monorepo starting with version 0.71.0, following the ongoing migration of Fuel tooling as outlined in the RFC.

Changes

• Add legacy_tarball_prefix field to Component struct for components that changed their packaging format
• Add tarball_prefix_for_version() method for version-aware tarball prefix resolution
• Update tag_for_version() to handle forc-crypto tags in forc monorepo
• Update download logic to use version-aware tarball prefix
• Update components.toml with forc-crypto migration config
• Update forc-wallet targets to use simplified naming convention (matching new forc repo releases)
• Refactor TargetTriple::from_component to derive target format from the component's targets field in components.toml, rather than using is_distributed_by_forc(). This is more flexible as components migrate to the forc monorepo with simplified target names.

Target Triple Format

The target naming format is now determined by the component's targets field in components.toml:

Format	Example	Components
Simplified	darwin_arm64, linux_amd64	forc, forc-wallet, forc-crypto
Rust triple	aarch64-apple-darwin, x86_64-unknown-linux-gnu	fuel-core, fuel-core-keygen

Version Routing

Version	Repository	Tarball	Tag Format
< 0.71.0	sway	forc-binaries-{target}.tar.gz	v{version}
≥ 0.71.0	forc	forc-crypto-{version}-{target}.tar.gz	forc-crypto-{version}

Related PRs

This is part of the broader effort to migrate Fuel tooling from the sway monorepo to the forc monorepo:

• RFC: Tooling Monorepo sway-rfcs#49
• forc-crypto migration: Migrate forc-tracing & forc-crypto over from the sway repo. forc#119
• fuel.nix forc-crypto: refactor: source forc-crypto from forc monorepo fuel.nix#205
• sway-nightly-binaries: feat: migrate forc-crypto nightly builds to forc monorepo sway-nightly-binaries#79
• Groundwork PRs:
  • feat: enable forc-wallet migration from standalone repo to forc monorepo #807 (forc-wallet migration)
  • feat: enable forc-wallet migration from standalone repo to forc monorepo fuel.nix#204 (forc-wallet in fuel.nix)
• Channel TOML updates: fix: rename forc-wallet targets from Rust triples to simplified names #811 (forc-wallet target renaming in gh-pages)

Test Plan

• cargo test -p component - all migration tests pass
• cargo test --lib - all 65 tests pass
• cargo clippy - no warnings
• Manual test: fuelup component add forc-crypto@0.71.0 (pending nightly release)
• Manual test: fuelup component add forc-crypto@0.70.1 (legacy version)

[github-actions]

LCOV of commit afc4816 during CI #2289

Summary coverage rate:
  lines......: 87.3% (2674 of 3064 lines)
  functions..: 62.0% (409 of 660 functions)
  branches...: 65.2% (283 of 434 branches)

Files changed coverage rate: n/a

[cursor]

PR Summary

Routes forc-crypto to the forc monorepo ≥0.71.0 with correct tags/tarballs, updates target triple resolution from component config, and adjusts override/install and configs accordingly.

• Component model:
  • Add legacy_tarball_prefix and tarball_prefix_for_version(); extend tag_for_version() to handle forc-crypto tags in forc.
• Channel/Download:
  • Use tarball_prefix_for_version() in ci/build-channel and download.rs for URL/tarball generation.
• Config (components.toml):
  • Migrate forc-crypto to repository_name = "forc" with legacy_repository_name = "sway", legacy_before = "0.71.0", tarball_prefix = "forc-crypto", and legacy_tarball_prefix = "forc-binaries"; mark publishable.
  • Rename forc-wallet targets to simplified linux_amd64|linux_arm64|darwin_amd64|darwin_arm64.
• CLI (override handling):
  • proxy_cli: for versioned overrides, install/link via Toolchain::add_component(...) instead of direct store path usage.
• Target triples:
  • TargetTriple::from_component now derives format from a component’s targets (simplified vs Rust triple); update tests accordingly.
• Tests:
  • Add migration tests for forc-crypto; make yesterday() dynamic; adjust override version defaults.

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

[cursor]

Bug: Target format not version-aware for migrated components

The TargetTriple::from_component function determines target format from the current components.toml configuration, but isn't version-aware. For forc-wallet, the targets changed from Rust triples (aarch64-apple-darwin) to simplified format (darwin_arm64). When downloading legacy versions (< 0.16.0), the code will use simplified targets, but those releases were published with Rust triple target names. This causes URL mismatches and download failures. Unlike repository_for_version and tarball_prefix_for_version, target format lacks version-specific handling.

Additional Locations (1)

• components.toml#L117-L118

 

[cursor]

Bug: Nightly build ignores legacy tarball prefix for migrated components

The write_nightly_document function uses component.tarball_prefix directly to match asset names from sway-nightly-binaries. After the forc-crypto migration, its tarball_prefix is now "forc-crypto", but nightly builds in sway-nightly-binaries still use the "forc-binaries" prefix. The code needs to also check legacy_tarball_prefix when matching nightly assets, otherwise forc-crypto won't be found in nightly channel builds.

ci/build-channel/src/main.rs#L194-L195

fuelup/ci/build-channel/src/main.rs

Lines 194 to 195 in afc4816

	// we want to store the download information in a channel.
	if let Some(stripped) = asset.name.strip_prefix(&component.tarball_prefix) {

 

---