v0.7.0

Fixed

• undo apply replays against the target the original write ran on. It dispatched the inverse against whatever target the caller named — in practice the config's first entry — while the write's own target sat unused in the undo record. On a multi-target config the inverse therefore ran against the wrong host; it only looks harmless because the resource usually is not there, but two hosts holding the same name and the inverse succeeds on the wrong one, silently. An explicitly named target still wins. Line-wide: all 24 copies had the identical defect. Caught live in container-host-aiops, where a stop recorded against a Podman target replayed against a Portainer one.

v0.6.0

Changed (BREAKING)

• Requires MCP SDK 2.0 (mcp[cli]>=2.0,<3.0). mcp.server.fastmcp no longer exists in 2.0; the server is now built with MCPServer and reports its package version in the stdio handshake.

Fixed

• undo apply works from the CLI. Every write tool is imported lazily inside its own CLI command, so a CLI-driven undo ran in a process where the inverse tool was never registered and failed with "inverse tool is not registered" — for every write tool. Only the MCP entry point, which imports the whole server, worked. Found while live-verifying against a real cluster.
• An undetermined outcome is audited unknown, not ok. The harness only classified a result as undetermined when the payload also carried an error key, so a write that looked successful but had not been confirmed was recorded as a success.
• as_int no longer round-trips integers through float64, which cannot represent values above 2**53 exactly. A line-wide sweep found only one of six vendored copies had actually been fixed after the original precision bug. The bool guard precedes the int short-circuit because bool subclasses int — otherwise True would be returned unchanged and serialised as true rather than a number.

v0.5.0

Release notes — cicd-aiops 0.5.0

Previous release: 0.4.0.

Live-verified against real GitLab CE 19.2

cicd's GitLab branch was pointed at a real current GitLab for the first time. Reads, the flagship RCA, a governed write (audited, real effect, undo reverted on the server), and the CLI audit path all checked out — and it surfaced the two list_projects field bugs fixed below.

In this tool

• Fixes two field bugs found live against real GitLab CE 19.2. list_projects now surfaces each project's name (it only mapped the path before), and reports byte counts (repoBytes / artifactsBytes / storageBytes) as integers — GitLab's repository_size was being rendered as a float (3870.0 bytes).

v0.4.0

Release notes — cicd-aiops 0.4.0

Previous release: 0.3.0.

BREAKING — the authorization layer is removed

This tool no longer decides whether a write is permitted. Read-only mode
(<PREFIX>_READ_ONLY), the graduated-approval / approver gate, and the
rules.yaml deny engine are all gone. Whether an operation runs is the
agent's judgement, or the permission of the account you connect it with — point
it at a read-only credential and the write fails at the server, the place that
actually owns the permission.

What the tool guarantees instead is that nothing is silent: every operation,
over MCP and the CLI alike, lands a row in the audit log — there is no
unaudited entry point. Destructive writes still capture their before-state and
record an undo token where a clean inverse exists.

• If you set <PREFIX>_READ_ONLY=1, it now has no effect and the MCP server
  logs a warning at startup. Restrict writes via the connecting account instead.
• <PREFIX>_AUDIT_APPROVED_BY / <PREFIX>_AUDIT_RATIONALE still work, but are now
  optional audit annotations — recorded on the row when set, never required.
• The declared risk_level is carried into the audit row as a descriptive tier
  (a label, not a gate).

The governance harness is now: audit (MCP+CLI, unbypassable) · runaway/budget
safety guard · undo recording · output sanitize. policy.py is a small
risk-tier classifier; governance/readonly.py is deleted.

v0.3.0

Release notes — cicd-aiops 0.3.0

Previous release: 0.2.1.

Every tool in the line: previews and undetermined outcomes

This release fixes three harness defects that were silently degrading the audit
trail and the undo store.

A write that loses its response is no longer recorded as a failure. The
harness assumed a sanitized error meant nothing had happened. That assumption is
false in exactly the case that matters most: when a write severs its own
connection, the request has already landed, the response cannot come back, and
the operation was recorded as status=error with no undo token created at
all. Transport-level failures are now audited as status=unknown, the result
says plainly that the operation may have taken effect and should be verified
before retrying, and a write that stashed its before-state has its inverse
recorded anyway — flagged effectVerified: false, which undo_list and
undo_apply both surface. Existing undo.db files are migrated in place; their
rows read as verified, which is accurate, since the old code only ever recorded
on the confirmed path.

A dry-run no longer writes an undo token. Previews were recording inverses
built from a before-state they never had: the undo callback's permissive default
filled the gap with a guess, producing a real, applicable token for an operation
that never happened.

A dry-run no longer demands a named approver. Requiring an approval in order
to ask whether something needs approval inverts what a preview is for. The tier
is still computed and still audited, so the preview can tell you an approver
will be needed; it just no longer refuses to answer. The write itself is gated
exactly as before.

The invariant, now stated: a dry_run may read; it must never write. Guards
run on the preview path, which means a preview can and does report that an
operation would be refused.

Also line-wide

• Truncated text now ends in an ellipsis instead of being cut silently. This
  line already treats a silent cut as a defect for lists; it was doing exactly
  that to strings.
• Error messages are capped at 800 characters, not 300. These messages end
  with what to do instead, so the cap was removing the most useful sentence of
  every long refusal.

v0.2.1

Release notes — cicd-aiops 0.2.1

Previous release: 0.2.0.

Fixed: unsupported resources were reported as a missing config key

Asking Gitea for a GitLab-only resource produced:

Error: Missing required key or environment variable: "Resource 'runners' is
not available on platform 'gitea'. Available resources: ..."

The correct explanation was inside the quotes, but the headline sent the reader
hunting a config/env problem that does not exist. The cause: "this platform has no
such resource" was signalled with a bare KeyError, and the CLI assumed every
KeyError meant a missing config key.

Unsupported resources now raise a dedicated UnsupportedResource — a KeyError
subclass, so any existing except KeyError keeps working — and the CLI reports it
as what it is. proxy-aiops already had this pattern (UnsupportedOperation); this
repo had diverged from it.

Live-verified

Against Gitea 1.27.0: doctor including the token-scope probe, reads
cross-checked against Gitea's API, and rca pipelines/stale/storage. See
docs/VERIFICATION.md — GitLab remains unverified and is
the richer branch (runners, job traces, artifact retention).

v0.2.0

Release notes — cicd-aiops 0.2.0

Previous release: 0.1.2.

Headline: read-only mode

export CICD_READ_ONLY=1

With this set the 7 write tools are never registered — an MCP
client lists 21 tools instead of 28. The writes are not hidden
behind a flag and not merely refused on call: they are absent from the session,
so a model cannot invoke one and cannot be argued into one. For a reviewer this
is checkable rather than promised — connect, list the tools, and the writes are
not there.

Enforcement is two layers deep: the @governed_tool harness refuses every
non-read operation (covering the CLI and in-process callers too), and the MCP
server removes write tools from list_tools(). Changing entry point does not
get around it.

BREAKING — return shapes changed

This release changes payloads that callers may be parsing. Both changes exist
to stop a result from misrepresenting itself:

1. Absent fields are now null, not "". A missing value and an empty value
   were previously indistinguishable, which invited consumers to invent the
   difference. Keys are still always present — only the value may be null.
2. Anything with a limit now returns an envelope —
   {"<items>": [...], "returned": N, "limit": L, "truncated": bool}. Truncation is
   measured (one extra row is fetched), never inferred from the page happening to
   be full. Where a genuine pre-cap total is knowable it is reported as total;
   where it isn't, total is deliberately omitted rather than echoing returned.

Also in this release

• docs/VERIFICATION.md — what the mock suite actually guarantees, a live
  verification checklist, and the criteria for claiming this tool verified.
• skills/cicd-aiops/references/agent-guardrails.md — for driving this tool with a
  smaller / local model: which guardrails are now enforced for you, and a
  ready-made system prompt for the rest.
• Expanded operator playbooks in the skill documentation.
• The advertised tool count now matches what an MCP client actually lists
  (it includes undo_list / undo_apply), and a release gate keeps it honest.
• The (preview) label has been dropped. It never meant unreleased; verification
  status now lives in docs/VERIFICATION.md where it can be specific.

v0.1.2

Fix: runner_health_rca now dispatches to the correct ops module (was AttributeError on live data). Coverage raised to ~91%.

v0.1.1

Adds the MCP Registry ownership marker (mcp-name) to the README so the server registers on the MCP Registry. No functional change.

v0.1.0

First release (preview). Governed AI-ops with the line's built-in audit + budget + undo + graduated-approval harness, secure-by-default. CLI + MCP server. See README for the support matrix and CHANGELOG for details.