Repository navigation
Releases
Releases · mickey-ichi/backlog-bridge
v0.1.9
- Edit and delete comments:
backlog-bridge comment-edit <ref> <commentId>/comment-delete, and the MCP tools
update_comment/delete_comment. The dry run shows the current comment. - Attachments:
--attach=path(repeatable) oncomment,createandupdateuploads images or files and attaches
them; the MCP tools take anattachmentslist of local paths. Files are uploaded only when sending, behind the
same secret-file guard as--file. backlog-bridge attachments <ref>,attachment-get(downloads to a temp folder) andattachment-delete, plus the
MCP toolslist_attachments,download_attachmentanddelete_attachment.attachment-getsaves into a fresh private temp folder (mkdtemp) unless--outis given.docs/mcp-tools.md(also in Tiếng Việt and 日本語): every MCP tool with its parameters, linked from the READMEs;
a test keeps it in step with the server.
v0.1.8
- Create and delete issues:
backlog-bridge create <space> <PROJECT> summary=...andbacklog-bridge delete <ref>,
plus the MCP toolscreate_issueanddelete_issue. Both are dry runs until--yes/send: true; the delete
dry run shows the issue that would go. create/updatetaketype,priority,category,milestone,versionandparentby name or key, besides
statusandassignee;--filefills the description (with the same secret-file guard ascomment --file).- The default statuses and priorities accept English, Japanese and Vietnamese names in any space
(In Progress=処理中=Đang xử lý). An unknown status now lists the project's real ones. search --openhides the Closed status in every language (it matched only the English name before).
v0.1.7
README (English, Tiếng Việt, 日本語): a centered header with the icon, a one-line summary and badges (npm, monthly downloads, CI, provenance, OpenSSF Scorecard, license). No code changes. Same contents as v0.1.6, which could not be published to npm during a Sigstore outage.
v0.1.6
Not published to npm: a Sigstore transparency-log outage blocked provenance signing. Use v0.1.7, which has the same contents.
v0.1.5
- Listed on the Official MCP Registry as
io.github.mickey-ichi/backlog-bridge:mcpNamein package.json,
server.jsongenerated bynpm run build, and the Release workflow publishes it after npm. - The
.mcpbships the icon; the Claude Desktop guide notes the extension covers Chat and Cowork.
v0.1.4
- Releases are automated: publishing a GitHub Release builds and attaches the
.mcpband publishes to npm via
Trusted Publishing (with provenance). npm fund/ GitHub Sponsors link; Support section in the READMEs.
Install
- Claude Desktop (Chat): download
backlog-bridge-0.1.4.mcpbbelow (attached by CI) → Settings → Extensions. Guide: docs/claude-desktop.md - Claude Code / terminal:
npm install -g backlog-bridge@latest. Guide: docs/claude-code.md
v0.1.3
- Claude plugin (
plugin/, built bynpm run build): the 4 skills plus the MCP server as a local
stdio server, for Claude Code and Cowork, ready to submit to the Claude plugin directory. Install locally with
claude --plugin-dir plugin. Chat still uses the Desktop Extension. - Claude Desktop Extension (
backlog-bridge-<version>.mcpb, attached to each GitHub Release): install with a
double-click; runs on Claude Desktop's built-in Node, so no Node/npm install is needed. Optional "Data folder"
setting (default~/.config/backlog-bridge). Build withnpm run pack:mcpb. - New MCP tool
create_data_folderandbacklog-bridge setup --data-only: create the data folder with a private
sample.env(first-time setup from Claude Desktop). Never overwrites, never handles keys. - MCP tools run the CLI in a worker thread instead of a child process, so they work on Claude Desktop's built-in
Node (whereprocess.execPathis the Claude app and every tool returned "(no output)"). - Unfilled host templates such as
${user_config.home_dir}are ignored instead of being used as a path. - Guide: docs/claude-desktop.md (English) and
docs/claude-desktop.vi.md(Vietnamese).
Install
- Claude Desktop (Chat): download
backlog-bridge-0.1.3.mcpbbelow → Settings → Extensions → drag it in → Install. Guide: docs/claude-desktop.md - Claude Code / terminal / Codex / Cursor:
npm install -g backlog-bridge && backlog-bridge setup. Guide: docs/claude-code.md - Claude plugin (Claude Code, Cowork):
plugin/in this repo —claude --plugin-dir plugin
v0.1.2 — npm install docs
backlog-bridge 0.1.2 — docs
backlog-bridge is now on npm:
npm install -g backlog-bridge
backlog-bridge setup- READMEs (English, Tiếng Việt, 日本語) document the npm registry install; update with
npm install -g backlog-bridge@latest, pin withbacklog-bridge@<version>. - The Windows hint in
backlog-bridge setuppoints to the npm install. - npm page links to the GitHub repo and issue tracker.
No code changes besides that hint. Full details: CHANGELOG.md
v0.1.1 — bug fix
backlog-bridge 0.1.1 — bug fix
- Fix: before
backlog-bridge setuphad run, an npm install used its own install directory as the home directory, sobacklog-bridge spacessuggested putting.envinside the npm package (lost on every update). The home directory is now always~/.config/backlog-bridgeunlessBACKLOG_BRIDGE_HOMEis set. backlog-bridge spaceswith no.envyet tells you to runbacklog-bridge setupfirst.
Install / update: npm install -g --install-links github:mickey-ichi/backlog-bridge#v0.1.1, then backlog-bridge setup.
Full details: CHANGELOG.md
v0.1.0 — first release
backlog-bridge 0.1.0 — first release
- CLI to read/write many Backlog spaces from one command; a URL or key picks the right space and key; writes are dry runs until
--yes. - Sync:
mirror(customer → internal) andprogress(internal progress → the customer's WBS) with safety rails. - AI agents: skills for Claude Code / Codex / Cursor, a per-user review mode for customer-facing text, and an MCP server for Claude Desktop and other hosts.
- Install:
npm install -g --install-links github:mickey-ichi/backlog-bridge#v0.1.0, thenbacklog-bridge setup. Runs on macOS, Linux and Windows. - Security: keys only in
.env, issue-key validation, secret-file refusal, and no flag smuggling through MCP.
Full details: CHANGELOG.md