LineBridge v0.7.11

Changes

This patch release includes PR #17, merged at b4815656c4d70d6f6deaf6e2385f0bb0d366c5ba, plus the synchronized application version bump.

Exact release/tag commit: 3d6a71140c2c27ca43ed7819a59a6321c4978b0f.

• Use the official JSR @evex/linejs 3.4.2, pinned with lockfile integrity. Preserve existing encrypted token, key, sequence and cursor records; missing keys during reads, monitoring or send preparation cannot trigger automatic key enrollment.
• Receive OpenChat notifications through one account feed, hydrating only designated rooms with at most two concurrent room tasks. The new default cooldown is 15 seconds with bounded jitter; existing saved intervals, including 60 seconds, are preserved. Durable room/account checkpoints retain baseline exclusion, available backfill and message deduplication.
• Rearm Talk 250 ms after durable success, with bounded anti-spin delays for repeated fast empty responses. Serialize monitor replacement while keeping login cancellation and durable ACKs responsive.
• Preserve safe HTTP/parse diagnostics and bounded Retry-After. Check both outer HTTP and decoded LEGY statuses, so an outer 200 containing inner 429/503 cannot become a successful poll. Account continuation pages cannot renew untouched rooms before the feed catches up.

Published platform

Windows x64 only: portable ZIP containing Node 26.5.0, the native tray, CLI and service. Extract the complete archive. Check the matching SHA-256 file and build metadata before use. Windows tray requires .NET Framework 4.8; the LineBridge tray binary is unsigned, as documented in PACKAGING.md.

No macOS or Linux asset was built or validated for this release. macOS arm64/x64 assets require a separate authorized native build and validation from this same release tag. This release does not install or restart an existing LineBridge service.

Validation and provenance

Built locally on Windows x64 using the repository's release helper, bundled Node 26.5.0 and checksum-verified npm 11.6.0. JavaScript syntax checks, 337/337 tests, HTTP with the official MCP client, and Windows portable build/smoke passed. Portable smoke exercised an extracted Unicode/spaced path without Node/npm on PATH, the bundled worker, scoped CLI access, synthetic sends, persistence and shutdown. GitHub Actions remained disabled.

The release assets include the ZIP, matching checksum, build metadata and a source-provenance record. Validation used synthetic accounts and temporary data; it is not live LINE reception, delivery or rendering evidence.

Windows ZIP SHA-256: 57fc691e501b5c471680d79bab57fb51500e9894ecfe88a0c1de0acee49d4a2e. The source-provenance record is a local build record, not a signed attestation.

Known limits

• The previous roughly 110-second Talk failures remain unexplained; this release is not claimed to fix that live symptom.
• LineJS 3.4.2 drops the original timeout on token-refresh recursion: an initial 180-second Talk request uses the SDK's 30-second default on its refreshed attempt. The request, refresh/persistence and replay do not share an overall 180-second deadline. This limitation is reproduced by a test and remains documented in CLI.md.
• A pending poll never renews success. Freshness remains the configured interval plus 60 seconds, so a valid held Talk request can become stale before its deadline. Inspect every stream's actual health and success timestamps after an approved upgrade.
• A failing OpenChat room can stall its account batch; reconciliation depends on backlog and LINE retention. The faster default can increase total requests for a small room count and is not a verified LINE quota. Live media/Flex rendering and complete historical coverage remain unverified.

Existing installation, private data, grants and credentials are not changed by publication. No real LINE message was sent during release validation.