Skip to content

build(devenv): Frame's dev shell and CI run on the fleet devenv - #34

Merged
fts-forge[bot] merged 2 commits into
mainfrom
feat/devenv-ci
Nov 2, 2026
Merged

fts-forge[bot] merged 2 commits into
mainfrom
feat/devenv-ci

Conversation

@fts-forge

@fts-forge fts-forge Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Moves Frame's dev shell and every CI step onto the fleet devenv (devenv-fleet 6113b65, kache wrapper, rustc 1.99.1). Two commits, cherry-picked onto main: the devenv setup, and the CI shape matched to Task's checks.yml. flake.nix stays in the repo; no workflow calls nix develop. Verified locally: rustc 1.99.1, kache wrapper, fleet-doctor, cargo check -p frame, cargo fmt --check, just boundary, workflow YAML parse.

fts-forge Bot added 2 commits November 2, 2026 15:29
The checks workflow follows Task's layout: concurrency keyed per PR, push
and dispatch; a hosted action for pull requests and a pool action for
pushes, chosen per job by runner.environment; a single aggregator job.
Every command is `devenv shell -- <command>`. Nothing calls `nix develop`.

Hosted runners install nix (devenv needs it) and devenv 2.4.0 from the
upstream tag. The pool installs devenv only when `command -v devenv` finds
none, and keeps its warm target dir under CI_CACHE_DIR per job. Neither
sets RUSTFLAGS, RUSTC_WRAPPER or sccache; .cargo/config.toml is unchanged.
@fts-forge
fts-forge Bot merged commit e8fc433 into main Nov 2, 2026
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.

0 participants