release: v0.1.6 (rename taskflow-mcp → taskflow-mcp-core + one-time upgrade-hint fix)#53
Merged
Conversation
The npm names `taskflow-mcp` and `taskflow-mcp-server` were squatted by an unrelated package, so the host-neutral MCP server ships as `taskflow-mcp-core`. Syncs the directory rename across dependency pins, workspace config, publish workflow, host adapters, and docs; fixes two stale references in CONTRIBUTING.md and the library RFC. Adapter bin names (codex-taskflow-mcp / claude-taskflow-mcp / opencode-taskflow-mcp) are unchanged. Part of the v0.1.6 release.
The session_start "built-in agents are no longer synced to .pi/agents/" hint claimed to be a one-time upgrade hint but had no persistence — it re-printed on every session as long as settings.json lacked a taskflow key and the project had .pi/agents/*.md. Track shown-state with a marker file (~/.pi/agent/.taskflow-upgrade-hint-shown), created atomically (flag "wx") right after the first print. Subsequent sessions skip the print. Best-effort: an unwritable agent dir only means the hint may show once more; it never blocks session startup.
…ixed The ba0249d change (marker file so the "built-in agents are no longer synced" hint stops repeating every session) shipped with the 0.1.6 release branch but was not yet noted in the changelog.
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.
Completes the 0.1.6 release (the first publish attempt half-published:
taskflow-core@0.1.6is already on npm, buttaskflow-mcp@0.1.6failed with npm E403 — the name was squatted — so the remaining 6 packages never published).What this PR contains
taskflow-mcp→taskflow-mcp-core(directory, dependency pins, workspace, publish workflow, host adapter imports, docs). The npm namestaskflow-mcp/taskflow-mcp-serverare squatted; the host-neutral MCP server ships astaskflow-mcp-core. Adapter bin names (codex-taskflow-mcp/claude-taskflow-mcp/opencode-taskflow-mcp) are unchanged.ba0249d, by @heggria): the pi-taskflow "built-in agents are no longer synced" hint now persists via a marker file (~/.pi/agent/.taskflow-upgrade-hint-shown) so it stops re-printing every session.taskflow-mcpreferences cleaned up inCONTRIBUTING.mdanddocs/rfc-library-reuse.md.Verification (local)
pnpm run typecheck→ 0 errorspnpm test→ 1140/1140 passpnpm run build→ all 7 packages emit distlibrary.mdpresent in skills-src and generatedAfter merge
The existing
v0.1.6tag (pointing at pre-rename04c587d) will be deleted and re-pointed at the merge tip, which re-triggerspublish.yml:taskflow-coreis skipped (idempotent — already published, code unchanged), andtaskflow-mcp-core+taskflow-hosts+pi-taskflow+codex-taskflow+claude-taskflow+opencode-taskflowpublish as 0.1.6.