docs: correct README signing, updater, and download claims for first release - #116
Merged
Merged
Conversation
…release The README understated Flint's trust posture and pointed at a dead download target. - "Self-signed installers can trigger SmartScreen / Gatekeeper warnings" described Windows as self-signed. Windows installers carry a public-trust Authenticode signature issued through Azure Trusted Signing and validate against the Microsoft-managed root with no certificate to install. Only macOS is unsigned; the caveat now says so. - "Code signing / updater keys may still be operator-configured" was stale. The updater pubkey and endpoint are configured and pass verify:release. - "In-app updater tracks the latest GitHub release" is wrong for 0.7.0. releases/latest skips prereleases, so the updater will not offer it. Match the note added to CHANGELOG in #115. - The Status link pointed at releases/latest, which 404s on the API and redirects to an empty releases index. Point at /releases and drop the "when available" hedge now that 0.7.0 ships. Also add CI, release, platform, and license badges, and state that 0.7.0 is the first public release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The README says installers are available, but no 0.7.0 release assets are currently published.
Get a fresh assessment by requesting another Copilot review.
Pull request overview
Documentation-only update correcting Flint 0.7.0 release, signing, updater, and download claims.
Changes:
- Updated README release, signing, updater, and installation guidance.
- Added project status badges and first-release messaging.
- Added an empty documentation changeset.
File summaries
| File | Reviewed changes |
|---|---|
README.md |
Updates release status, signing, updater, download, and limitation documentation. |
.changeset/docs-readme-release-accuracy.md |
Records the documentation-only change without a version bump. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
joelst
added a commit
that referenced
this pull request
Sep 14, 2026
…nClaw (#117) * feat(integrations): surface the WSL2 mirrored-networking step for OpenClaw Flint already ships a complete one-click fix for this in Settings -> Network -> WSL clients: it detects WSL presence and mode, writes .wslconfig with a backup, and offers the WSL restart. The problem was finding it. The pointer lived in the OpenClaw card's `limitations` array, which renders only after clicking "Show limitations & docs". WSL2's default NAT mode gives the VM its own loopback, so a copied snippet fails with a connection error and the remedy is behind a disclosure nobody expands when things are already not working. That is the most likely first-run failure for OpenClaw on Windows, and OpenClaw is a headline integration for this release. Move the caveat into the card description so it is visible without expanding anything, and reduce the limitations entry to the manual NAT alternative so the card does not state it twice. Data-only change to the integrations catalog; no component or runtime changes. Also document the setting in the user guide: a WSL clients row in the network table, a subsection explaining why loopback fails under NAT, and a troubleshooting row. Corrects the guide's stale "self-signed builds" line in passing, matching the README fix in #116 — Windows installers are publicly trusted, though a new publisher identity can still draw a SmartScreen prompt. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #115. The README pitch, tables, and screenshots are unchanged — this fixes statements that were inaccurate, most of them in the direction of underselling Flint, plus one dead download target.
What was wrong
verify:release.releases/latestskips prereleases, so the updater will not offer it. This also contradicted the note added toCHANGELOG.mdin #115.releases/latest/releases.Also added
include_prereleases, so it picks up 0.7.0), platforms, license. A repo with no badges and no releases reads as unlaunched regardless of the copy quality.The SmartScreen point is kept but corrected: public trust removes the "unknown publisher" prompt, though a new publisher identity can still accumulate reputation over early downloads. That is accurate rather than alarming.
Verification
npm run verify:markdown-links— 135 relative links across 28 files🤖 Generated with Claude Code