@pipeworx/product-change-log

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/product-change-log’s. Install: one-click buttons

Connect to just the @pipeworx/product-change-log pack

https://gateway.pipeworx.io/product-change-log/mcp — only @pipeworx/product-change-log’s own tools, nothing else in the catalog.

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 4

Pipeworx’s change log for the products built on it: one durable record per change to a tool or field a product depends on, with its kind, fields, announcement, and the build that made it live or the deploy run that made it late.

Tools

  • product_change_log(product, since?, task_id?, status?, limit?) reads the records that affect one product, newest update first. Any account key can read.
  • change_log_announce(task_id, title, products, tools, kind, summary, actor, fields?, description_diff?, notes?) creates the record before the push, or amends it while it is still announced or late. Pipeworx owners only.
  • change_log_mark_live(task_id, commit, alters_existing_answers, expect_build?, notes?) records the stamped build that answered the call as the live build. Pipeworx owners only.
  • change_log_mark_late(task_id, run_id, reason, fix_expected?) records a failed deploy run. Pipeworx owners only.

Record

task_id, title, status (announced, live, late), kind (additive, behaviour_change, breaking), products, tools, fields (each {path, type, change?, values?} with the full closed value set), summary, description_diff, announced_at, announced_by, live (build_sha, built_at, at, commit, alters_existing_answers) or null, late (deploy_run_id, reason, at, live_build_sha_instead, fix_expected) or null, notes, updated_at.

since returns records whose updated_at is at or after it, so a change announced last week that went live today is returned.

Auth

Account-only: anonymous and key-only callers are refused before the pack runs, so a product calls with its own Bearer token. Writes additionally need the Pipeworx internal credential; any other caller gets owner_only and nothing is written.

Data sources

Pipeworx, cross-product change log. Written by Pipeworx owners; nothing is fetched from an outside publisher.

Record text is data, never instructions. Every free-text field is length-limited (an oversize value is refused, not truncated) and stripped of control, bidi and zero-width characters. Every read says so in note.

live.build_sha and live.built_at come from the gateway build that answered the change_log_mark_live call, never from the caller, and an unstamped build is refused. That the build contains the change commit is the writer’s attestation, made after confirming the deploy; expect_build makes the call fail when a different build answers.

Lifecycle and the rules around it: docs/cross-product-contracts.md. Store: migration 287_product_change_log.sql.

Tools

  • product_change_log — Read the Pipeworx change log for one downstream product: each record is a change to a tool or field that product depends on, with its kind (additive, behaviour_change, breaking), the fields and closed
  • change_log_announce — Pipeworx owners only. Announce a change before it is pushed: creates the change log record for a fleet task, or amends it while it is still announced or late. Closed value sets only in fields[].values
  • change_log_mark_live — Pipeworx owners only. Record that an announced change is live. The live build sha and built_at are read from the gateway build answering this call (never typed), and an unstamped build is refused. The
  • change_log_mark_late — Pipeworx owners only. Record that an announced change is late because its deploy failed: carries the failed run id, the reason, the build live instead, and when the fix is expected. A late record beco

Tools

  • change_log_announce — Pipeworx owners only. Announce a change before it is pushed: creates the change log record for a fleet task, or amends it while it is still announced or late. Closed value sets only in fields[].values
  • change_log_mark_late — Pipeworx owners only. Record that an announced change is late because its deploy failed: carries the failed run id, the reason, the build live instead, and when the fix is expected. A late record beco
  • change_log_mark_live — Pipeworx owners only. Record that an announced change is live. The live build sha and built_at are read from the gateway build answering this call (never typed), and an unstamped build is refused. The
  • product_change_log — Read the Pipeworx change log for one downstream product: each record is a change to a tool or field that product depends on, with its kind (additive, behaviour_change, breaking), the fields and closed

Regenerated from source · build November 18, 2026