chore: follow felis to the v0.1.0 release #10

Merged

natsukium merged 3 commits from follow-felis-v0.1.0 into main

2026-09-26 20:57:56 +09:00

natsukium commented

2026-09-26 19:07:37 +09:00

Owner

Pins every felis crate to the v0.1.0 release tag on https://github.com/felis-terminal/felis (not on crates.io). The old pin was d84ba1b4. deny.toml now allows the GitHub source instead of the private repository.

Depends on natsukium/felis-fcast#6. felis-fcast is pinned to that PR's head commit (6d8367d8), which follows felis to v0.1.0 too. Without that pin, the lockfile would pull a second copy of the felis crates from the private source. After felis-fcast#6 merges, re-pin felis-fcast to the merged commit on main, because a squash merge leaves the branch commit off main.

No code changes were needed: renderer_effect, the renderer and the felis-json types kept their APIs between d84ba1b4 and v0.1.0. The .fcast format did not change, so the fixtures stay as they are.

Verification

cargo fmt --all --check, cargo clippy --all-targets --all-features -- -D warnings, cargo test --all-features (16 unit tests plus 4 golden tests on lavapipe; all golden frames still match byte for byte), cargo deny check: all pass.
Live check: I recorded a session from an isolated v0.1.0 felis-daemon with felis-fcast#6's record, then rendered it with this branch to PNG frames and a GIF. The output shows the recorded text with its SGR color.

Pins every felis crate to the `v0.1.0` release tag on https://github.com/felis-terminal/felis (not on crates.io). The old pin was `d84ba1b4`. `deny.toml` now allows the GitHub source instead of the private repository. **Depends on natsukium/felis-fcast#6.** `felis-fcast` is pinned to that PR's head commit (`6d8367d8`), which follows felis to v0.1.0 too. Without that pin, the lockfile would pull a second copy of the felis crates from the private source. After felis-fcast#6 merges, re-pin `felis-fcast` to the merged commit on `main`, because a squash merge leaves the branch commit off `main`. No code changes were needed: `renderer_effect`, the renderer and the felis-json types kept their APIs between d84ba1b4 and v0.1.0. The `.fcast` format did not change, so the fixtures stay as they are. ## Verification - `cargo fmt --all --check`, `cargo clippy --all-targets --all-features -- -D warnings`, `cargo test --all-features` (16 unit tests plus 4 golden tests on lavapipe; all golden frames still match byte for byte), `cargo deny check`: all pass. - Live check: I recorded a session from an isolated v0.1.0 `felis-daemon` with felis-fcast#6's `record`, then rendered it with this branch to PNG frames and a GIF. The output shows the recorded text with its SGR color.

natsukium added 1 commit

2026-09-26 19:07:37 +09:00

chore: follow felis to the v0.1.0 release

ci / cargo fmt / clippy / test / deny (pull_request) Has been cancelled

Details

83e83f7681

felis is now published as a tagged release on GitHub rather than as
revisions of the private repository, and its crates are not on
crates.io, so every felis crate is pinned to the v0.1.0 tag of
https://github.com/felis-terminal/felis and cargo-deny allows that
source instead of the private one.

felis-fcast moves to the commit that follows felis to v0.1.0 as well.
Its parser keeps frame bodies opaque, so an older felis-fcast would
still work, but it would pull a second copy of the felis crates from a
source this repository no longer allows. The .fcast format did not
change, so the fixtures stay as they are, and the golden frames still
match byte for byte: nothing between the old pin and v0.1.0 changed
what the renderer draws for them.

Assisted-by: Claude Code

natsukium added 1 commit

2026-09-26 20:45:59 +09:00

ci: run on the x86_64-linux runner label

ci / cargo fmt / clippy / test / deny (pull_request) Successful in 54s

Details

9b9856461a

The Forgejo runners were re-registered with labels named after Nix
systems (nix -> x86_64-linux, macos -> aarch64-darwin), so jobs asking
for the old labels sit in the queue with no runner to pick them up.

Assisted-by: Claude Code

natsukium added 1 commit

2026-09-26 20:54:11 +09:00

chore: pin felis-fcast to its merged v0.1.0 follow

ci / cargo fmt / clippy / test / deny (pull_request) Successful in 56s

Details

8b0fd088ef

felis-fcast#6 was squash-merged as 24e7ba08, so the PR-head commit
6d8367d8 this branch pinned is no longer on any branch there and could
be garbage-collected.

Assisted-by: Claude Code

natsukium merged commit 7a8a702b0c into main

2026-09-26 20:57:56 +09:00

natsukium referenced this pull request from a commit

2026-09-26 20:57:57 +09:00

chore: follow felis to the v0.1.0 release (#10)

natsukium deleted branch follow-felis-v0.1.0

2026-09-26 21:17:38 +09:00