natsukium/felis-docs
Watch
1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore: follow felis to v0.1.0 #2

Merged
natsukium merged 4 commits from follow-felis-v0.1.0 into main 2026-09-26 21:01:02 +09:00
Conversation 0 Commits 4 Files changed 10 +62 -157
natsukium commented 2026-09-26 19:46:37 +09:00
Owner
Copy link

Brings the docs site to the released felis v0.1.0.

Changes

  • vendor/felis: the submodule now tracks https://github.com/felis-terminal/felis and sits on v0.1.0 (fc720338), up from 105b0899. The docs tree kept the same top-level layout (explanation/, how-to/, reference/, tutorials/, README.md), so the symlinks and sidebar needed no changes.
  • flake.lock: felis-web-component is locked to 0c33110 on its follow-felis-105b0899 branch. That branch locks felis to github:felis-terminal/felis/v0.1.0 (fc720338) and felis-web-gateway to dadcf2b on its follow-felis-v0.1.0 branch.
  • Links to felis itself (README, landing page, ecosystem card, the Source social link, edit-page links, and out-of-docs links rewritten by remark-felis-links) now go to GitHub. The rewriter builds /blob/main/… URLs, and the edit link uses /edit/main/docs/…. Ecosystem repos stay on git.natsukium.com.

Needs re-locking after the sibling PRs merge

felis-web-component PR #3 and felis-web-gateway PR #4 are still open, so this lock points at their branch tips. flake.nix still tracks main. Once both PRs merge (gateway first, then component re-locked to gateway main), run nix flake update felis-web-component here so the lock points at main.

Verification

  • nix build .#devShells.x86_64-linux.default: OK. This builds the felis-web-component 0.1.0 web bundle.
  • nix flake check: all checks passed.
  • nix develop -c npm ci && npm run check: 0 errors, 0 warnings, 0 hints.
  • nix develop -c npm run build: complete, 65 pages.
  • nix develop -c npm run linkcheck: 94 links scanned, all OK.
  • Spot-checked dist/reference/ipc/index.html for text added in v0.1.0: it contains the daemon.sock.agent paragraph and "peer-UID pair", which replaces the old "SO_PEERCRED pair". Its edit link is https://github.com/felis-terminal/felis/edit/main/docs/reference/ipc.md.
  • All 7 distinct rewritten github.com/felis-terminal/felis/blob/main/… links in the built site return 200.
Brings the docs site to the released felis v0.1.0. ## Changes - `vendor/felis`: the submodule now tracks https://github.com/felis-terminal/felis and sits on `v0.1.0` (`fc720338`), up from `105b0899`. The docs tree kept the same top-level layout (`explanation/`, `how-to/`, `reference/`, `tutorials/`, `README.md`), so the symlinks and sidebar needed no changes. - `flake.lock`: `felis-web-component` is locked to `0c33110` on its `follow-felis-105b0899` branch. That branch locks felis to `github:felis-terminal/felis/v0.1.0` (`fc720338`) and `felis-web-gateway` to `dadcf2b` on its `follow-felis-v0.1.0` branch. - Links to felis itself (README, landing page, ecosystem card, the Source social link, edit-page links, and out-of-docs links rewritten by `remark-felis-links`) now go to GitHub. The rewriter builds `/blob/main/…` URLs, and the edit link uses `/edit/main/docs/…`. Ecosystem repos stay on git.natsukium.com. ## Needs re-locking after the sibling PRs merge `felis-web-component` PR #3 and `felis-web-gateway` PR #4 are still open, so this lock points at their branch tips. `flake.nix` still tracks main. Once both PRs merge (gateway first, then component re-locked to gateway main), run `nix flake update felis-web-component` here so the lock points at main. ## Verification - `nix build .#devShells.x86_64-linux.default`: OK. This builds the `felis-web-component` 0.1.0 web bundle. - `nix flake check`: all checks passed. - `nix develop -c npm ci && npm run check`: 0 errors, 0 warnings, 0 hints. - `nix develop -c npm run build`: complete, 65 pages. - `nix develop -c npm run linkcheck`: 94 links scanned, all OK. - Spot-checked `dist/reference/ipc/index.html` for text added in v0.1.0: it contains the `daemon.sock.agent` paragraph and "peer-UID pair", which replaces the old "`SO_PEERCRED` pair". Its edit link is `https://github.com/felis-terminal/felis/edit/main/docs/reference/ipc.md`. - All 7 distinct rewritten `github.com/felis-terminal/felis/blob/main/…` links in the built site return 200.
felis v0.1.0 is released from the public repository at
github.com/felis-terminal/felis, whose history is a fresh squashed import;
the private repository the submodule tracked is archived. The site should
publish the released docs, so the vendor/felis submodule now tracks the
public repository and sits on the v0.1.0 commit.

The web component bundle embedded in the docs is re-locked to the
felis-web-component branch that follows felis to v0.1.0 (which in turn
locks felis to github:felis-terminal/felis/v0.1.0 and felis-web-gateway
to its own v0.1.0 follow branch). Those follows are still open pull
requests, so this lock points at branch tips and must be re-locked to main
once they merge; flake.nix itself keeps tracking main.
docs: link felis on GitHub
Some checks failed
ci / astro check + link check (pull_request) Has been cancelled
Details
6a3434fc0e
 
The public face of felis is now github.com/felis-terminal/felis; the
Forgejo repository the site linked to is private. Source, edit-page and
out-of-docs links therefore go to GitHub, and the repository-browse shape
the link rewriter builds switches from Forgejo's /src/branch/ to GitHub's
/blob/. Ecosystem repositories stay on git.natsukium.com, where they live.
ci: run on the x86_64-linux runner label
All checks were successful
ci / astro check + link check (pull_request) Successful in 28s
Details
98e3bff14f
 
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.
chore: lock felis-web-component to main
All checks were successful
ci / astro check + link check (pull_request) Successful in 26s
Details
b8e08f1564
 
felis-web-component#3 and felis-web-gateway#4 have merged, so the lock
leaves their PR branches (which the squash merges leave behind) for
main; felis stays at v0.1.0 through the component's own lock.
natsukium referenced this pull request from a commit 2026-09-26 21:01:04 +09:00
chore: follow felis to v0.1.0 (#2)
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
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
natsukium/felis-docs!2
No description provided.