chore(main): release 0.9.0#131
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
50d8d76 to
a417e94
Compare
dfrostar
pushed a commit
that referenced
this pull request
May 18, 2026
…page consistency 5 actionable groups from Copilot review (1 timing-related group handled by merge ordering, see PR description): Group B + C — internal Docker inconsistency: - README.md Quick Start install matrix Docker row: replaced `docker build -t neuralmind:dev .` example with `docker pull ghcr.io/dfrostar/neuralmind:latest`. Kept the local- build path as a follow-up sentence. The hero callout (line 14) and the install matrix (line 454) now agree on GHCR being the primary Docker path. - docs/wiki/Setup-Guide.md Docker row: same fix as the README install matrix. The companion setup matrix in the wiki no longer presents a different Docker install path from Installation.md. Group D — "Windows Task Scheduler templates" wording: - Was technically wrong — Windows support shipped as a Scheduling-Guide walkthrough, not as committed template files (only systemd + launchd ship as committed templates under scripts/). - Reworded in 3 spots (README hero callout, README Resources table, docs/wiki/Home.md v0.8 What's New) to say "systemd + launchd templates + a Windows Task Scheduler walkthrough in the Scheduling Guide" — matches what actually shipped. Group E — `neuralmind-mcp /project` arg silently ignored: - Verified against neuralmind/mcp_server.py:458 — main() takes no arguments and never reads sys.argv. Each MCP tool call carries its own project_path in the request payload (see tool_wakeup, tool_query, etc. at mcp_server.py:69+). - docs/wiki/Installation.md Docker MCP example: dropped the misleading `/project` positional, added a comment explaining the MCP arg model (server ignores argv; tool calls carry project_path). The mount is still useful — it exposes the project tree so tool calls can find the path. Group F — index.html "Walkthrough →" CTA pointing at the About summary: - The CTA was labeled "Walkthrough →" but pointed at about.html#whats-new-v090 (another summary). Split into two CTAs: "Air-gapped walkthrough →" links to docs/use-cases/air-gapped.md (the actual walkthrough), and "Summary →" keeps the About anchor. Group A — Copilot flagged "v0.9.0 advertised but pyproject says 0.8.0" in 6 places (README/Home/about/index/ROADMAP/Installation). This is a timing artifact: release-please PR #131 bumps pyproject to 0.9.0 + creates the v0.9.0 tag. Resolved by merge ordering — see PR description for the recommended sequence (#131 first, then #132). No wording changes; the docs accurately reflect post-merge state. https://claude.ai/code/session_01SH6iHNAqeMJHXdq7ubVcuJ
Contributor
Author
|
🤖 Created releases: 🌻 |
dfrostar
added a commit
that referenced
this pull request
May 18, 2026
…132) Structural doc rollout matching what v0.7.0 had. v0.8.0 + v0.9.0 shipped to main but user-facing surfaces were still framed around v0.7.0. Marketing artifacts (LinkedIn drafts, NotebookLM packs, screencast scripts) explicitly deferred per "ship code + minimum docs, marketing arc later" cadence. - README.md: hero callout cascade v0.9.0 (top) → v0.8.0 → v0.7.0 → v0.6.0. Resources table updated. Quick Start install matrix Docker row now uses GHCR. - docs/wiki/Home.md: v0.9.0 + v0.8.0 "What's New" entries above v0.7.0. Windows Task Scheduler wording precision (it's a Scheduling Guide walkthrough, not committed template files). - docs/wiki/Installation.md + docs/wiki/Setup-Guide.md: Docker rows use `docker pull ghcr.io/dfrostar/neuralmind:latest` (auto-published since v0.9.0); local-build path preserved as a callout. Docker section's neuralmind-mcp example dropped the ignored /project arg with a comment explaining the MCP arg model. - docs/about.html: new whats-new-v090 + whats-new-v080 sections above whats-new-v070. - docs/index.html: Pages hero leads with v0.9.0. CTAs split into "Air-gapped walkthrough →" (the actual doc) + "Summary →" (the About anchor). - ROADMAP.md: "Shipped in v0.9.0" + "Shipped in v0.8.0" sections; removed completed "Now (v0.8)" + "Then (v0.8.x)" planning. New "Now — marketing rollout" + "Next" sections. 13 Copilot review items addressed in commit 3b11fd5. The "v0.9.0 advertised before pyproject bumped" set (6 comments) resolved by the merge ordering: #131 (release-please v0.9.0) merged first. https://claude.ai/code/session_01SH6iHNAqeMJHXdq7ubVcuJ
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
1 participant
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.
🤖 I have created a release beep boop
0.9.0 (2026-05-18)
Features
This PR was generated with Release Please. See documentation.