release: require the workspace version only on the binary crates #196

Merged

natsukium merged 1 commit from release/publish-prep into main 2026-10-19 22:23:45 +09:00

Conversation 0 Commits 1 Files changed 4 +46 -21

natsukium commented 2026-10-19 19:57:35 +09:00

Owner

Copy link

Part of #160 (policy amendment): library crates will take their own versions, and only felis-cli, felis-client and felis-daemon carry the app version the release tag names.

• tools/release/verify.py checks version.workspace = true only on the three binary crates (looked up by package name) and fails when one is missing; other crates may pin their own version.
• Self-test: a library crate on its own version passes, a pinned binary crate fails, a missing binary crate fails.
• docs/reference/workspace.md "Release gate" item 4 and tools/README.md describe the narrowed check. The "Versioning" section still says every member inherits, which stays true until the library crates switch versions.

Part of #160 (policy amendment): library crates will take their own versions, and only felis-cli, felis-client and felis-daemon carry the app version the release tag names. - `tools/release/verify.py` checks `version.workspace = true` only on the three binary crates (looked up by package name) and fails when one is missing; other crates may pin their own version. - Self-test: a library crate on its own version passes, a pinned binary crate fails, a missing binary crate fails. - `docs/reference/workspace.md` "Release gate" item 4 and `tools/README.md` describe the narrowed check. The "Versioning" section still says every member inherits, which stays true until the library crates switch versions.

natsukium added 1 commit 2026-10-19 19:57:35 +09:00

release: require the workspace version only on the binary crates ... b5c4776ec6

Under the #160 amendment the library crates take their own versions,
starting at 0.1.0, while felis-cli, felis-client and felis-daemon carry
the app version the release tag names. The tag check refused any crate
that did not inherit [workspace.package] version, so it would block the
first release with decoupled libraries. It now checks only the three
binary crates, and fails when one of them is missing rather than
passing a renamed crate silently.

Assisted-by: Claude Code

natsukium referenced this pull request 2026-10-19 20:20:58 +09:00

workspace, ci, docs: make every crate publishable and package them in CI #197

natsukium force-pushed release/publish-prep from b5c4776ec6 to 683107a3f7 2026-10-19 22:23:32 +09:00 Compare

natsukium merged commit 2f137a29ed into main 2026-10-19 22:23:45 +09:00

natsukium deleted branch release/publish-prep 2026-10-19 22:23:45 +09:00

natsukium referenced this pull request from a commit 2026-10-19 22:23:46 +09:00

Merge pull request 'release: require the workspace version only on the binary crates' (#196) from release/publish-prep into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

Area/ci

CI workflows (.forgejo/workflows/)

  

Area/cli

felis-cli crate, the felis front-door binary

  

Area/client

felis-client crate, the winit GUI frontend

  

Area/client-core

felis-client-core crate, shadow screen, config, connect_or_spawn_daemon

  

Area/daemon

felis-daemon crate, session pool, IPC server

  

Area/deps

Dependency bumps

  

Area/docs

Documentation tree when no narrower area fits

  

Area/grid

felis-grid crate, cells, scrollback, image store

  

Area/manual

User-facing docs: tutorials, how-to, user-facing reference pages

  

Area/nix

Nix flake, home-manager module, package definitions

  

Area/protocol

felis-protocol crate, felis.proto, frame layout, version constants

  

Area/pty

felis-pty crate, PTY backends

  

Area/render

felis-render-wgpu crate, GPU pipeline, atlas

  

Area/shaping

felis-shaping crate, swash shaper, font fallback

  

Area/skills

Agent skills (skills/felis, .agents/skills/)

  

Area/transport

felis-transport crate, framing, socket/pipe, SSH carrier

  

Area/vt

felis-vt crate, VT parser, dispatch

  

Compat/Breaking

Breaking change that won't be backward compatible

  

Kind/Bug

Something is not working

  

Kind/Documentation

Documentation changes

  

Kind/Enhancement

Improve existing functionality

  

Kind/Feature

New functionality

  

Kind/Performance

Throughput, latency, or memory cost

  

Kind/Security

This is security issue

  

Kind/Testing

Issue or pull request related to testing

  

perf-regression-accepted

Passes the instruction-count bench gate for an intended cost; state why in a PR comment

  

Reviewed

Confirmed

Issue has been confirmed

  

Reviewed

Duplicate

This issue or pull request already exists

  

Reviewed

Invalid

Invalid issue

  

Reviewed

Won't Fix

This issue won't be fixed

  

Status

Blocked

Something is blocking this issue or pull request

  

Status

Need More Info

Feedback is required to reproduce issue or to continue work

  

Status

Upstream

Waiting on a change in an upstream project

No labels

Area/ci

Area/cli

Area/client

Area/client-core

Area/daemon

Area/deps

Area/docs

Area/grid

Area/manual

Area/nix

Area/protocol

Area/pty

Area/render

Area/shaping

Area/skills

Area/transport

Area/vt

Compat/Breaking

Kind/Bug

Kind/Documentation

Kind/Enhancement

Kind/Feature

Kind/Performance

Kind/Security

Kind/Testing

perf-regression-accepted

Reviewed

Confirmed

Reviewed

Duplicate

Reviewed

Invalid

Reviewed

Won't Fix

Status

Blocked

Status

Need More Info

Status

Upstream

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

felis-terminal/felis!196

No description provided.