| Comment: | chore: bump submodule pins (bridge/v0.0.3) |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk | v0.0.13 |
| Files: | files | file ages | folders |
| SHA3-256: |
5a798c1a3645932fe532cbe12a697aa2 |
| User & Date: | 41898282+github-actions[bot]@users.noreply.github.com on 2026-05-05 00:41:00.000 |
| Other Links: | manifest | tags |
|
2026-05-05
| ||
| 15:42 |
fix(hub): periodic WAL checkpoint so vanilla fossil can read hub.fossil (#144)
Hub.fossil opens in WAL journal mode, so without checkpointing the on-disk file stays as a 4 KiB stub plus a multi-hundred-KiB *-wal sidecar — vanilla fossil tooling (fossil ui / fossil info / fossil timeline) refuses it because its validity probe stats the main file before consulting the WAL. Wire a goroutine in NewHub that runs PRAGMA wal_checkpoint(PASSIVE) every Config.CheckpointInterval (default 10s) so vanilla fossil can always read hub.fossil while the hub is running. PASSIVE never blocks readers or writers. Hub.Stop drains the goroutine before closing the libfossil handle; libfossil v0.6.0's own (*Repo).Close runs a TRUNCATE checkpoint, so the post-Stop on-disk file is self-contained. Closes #143. Bumps libfossil v0.5.0 → v0.6.0 (danmestas/libfossil#28). check-in: 72cfc528b2 user: [email protected] tags: trunk, v0.0.14 | |
| 00:41 | chore: bump submodule pins (bridge/v0.0.3) check-in: 5a798c1a36 user: 41898282+github-actions[bot]@users.noreply.github.com tags: trunk, v0.0.13 | |
|
2026-05-04
| ||
| 23:42 |
chore: bump actions/checkout v4→v6 + actions/setup-go v5→v6 (#142)
Quiets the Node.js 20 deprecation annotation that surfaced on the auto-release.yml dry-run. v6 of both actions ships on Node.js 24, ahead of the June 2026 forced-upgrade. No behavior change expected — same API surface. check-in: 0707c5f3d4 user: [email protected] tags: trunk, bridge/v0.0.3 | |