Skip to content

dl4rce/flaiwheel

v3.9.3 Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 3mo MCP Search & Web
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Affected surfaces

breaking_upgrade

Summary

AI summary

Fixed silent fast‑path bypass when checking for updates due to stale LATEST_VERSION fetch.

Full changelog

Bug fix

LATEST_VERSION was fetched from the pinned installer tag (v${_FW_VERSION}) rather than main. This caused a silent fast-path bypass:

  1. User runs curl ... | bash → gets main with _FW_VERSION=3.9.1 → re-pins to v3.9.1 → builds container at 3.9.1
  2. 3.9.2 and 3.9.3 are released
  3. User runs curl ... | bash again → gets main with _FW_VERSION=3.9.3 → re-pins to v3.9.3 → but LATEST_VERSION is fetched from v3.9.3 tag = 3.9.3, while container reports 3.9.1 → update triggered ✓

However if the user had a cached temp file from step 1 still on disk (edge case), _FW_VERSION would still be 3.9.1, LATEST_VERSION would fetch 3.9.1 from the old tag, match the running container, and silently fast-path.

Fix: always fetch LATEST_VERSION from main — the single source of truth for the latest release.

Upgrade

curl -sSL https://raw.githubusercontent.com/dl4rce/flaiwheel/main/scripts/install.sh | bash
View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track dl4rce/flaiwheel

Get notified when new releases ship.

Sign up free

About dl4rce/flaiwheel

Self-hosted memory and governance layer for AI coding agents. 28 MCP tools with structured knowledge capture, hybrid search (semantic + BM25 + cross-encoder reranking), behavioral documentation nudges, cold-start codebase analyzer, and git-native storage. Single Docker container, zero cloud dependencies.

All releases →

Related context

Beta — feedback welcome: [email protected]