Skip to content

v1.1.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Jul 13:23
v1.1.0
c8b84cd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The first feature release after 1.0.0. Everything here is additive — no
existing command changes its shape, so upgrading is a drop-in replacement.

Added

  • kuberoutectl mcp — an optional Model Context Protocol
    server over stdio, so an MCP-capable AI client can drive the safe core of the
    inventory (list targets, inspect credential health, manage collections). Opt-in:
    nothing runs unless you start it. --read-only exposes the inspection tools
    only. (#98, closes #44)
  • --verbose / -v (global) — traces every external CLI invocation, its exit
    code, and its stderr on failure. Turns "discovery found nothing" from a guess
    into something you can read. (#99)
  • A generated command reference on the docs site, produced from the Cobra
    command tree so it cannot drift from the binary. (#94)

Fixed

  • AWS: modern sso_session profiles are now recognised as SSO. A profile
    using the sso_session form (rather than the legacy inline sso_start_url) was
    classified as unknown health with no suggested action; it is now reported as
    expired with a renew action, so aws sso login is actually offered. (#101)
  • AWS: expired-token diagnostic. A failed identity check now says the token
    has likely expired and names the exact aws sso login --profile <name> to run,
    instead of silently yielding zero clusters. (#99)

Changed

  • Snapshot builds publish fixed-name macOS archives, so the rolling Homebrew cask
    for development keeps working across snapshots. Stable releases unaffected. (#100)

Verified

  • Unit tests, make check, and scripts/e2e.sh green on the tagged commit
    (c8b84cd) via ci.yml on main.
  • The published linux_arm64 artifact was downloaded, checksum-verified
    against checksums.txt, and exercised directly: it reports
    1.1.0 (commit c8b84cd), and answers a real MCP stdio handshake
    (initialize → notifications/initialized → tools/list), with --read-only
    correctly withholding the write tools.

Not verified

  • Build reproducibility was not checked when this tag was cut — the two-run
    make snapshot diff was skipped at release time. It was run afterwards, on
    2026-07-26, and passed    : two consecutive snapshot builds produced an
    identical dist/checksums.txt, covering the archives and the .deb / .rpm
    packages.

    That run was made on the development branch, not on this tag's commit
    (c8b84cd), so it is not a direct verification of these artifacts. It does
    exercise the same build configuration — mod_timestamp +
    SOURCE_DATE_EPOCH, unchanged between the two points — so the reproducibility
    guarantee in RELEASING.md is supported for this release, just indirectly.
    From v1.1.1 onward the check runs before the tag.

  • No third-party MCP client (Claude Desktop and friends) is exercised by the
    test suite. The stdio protocol itself is verified end to end against the
    shipped binary, but a real client integration is not.

  • No provider tool runs against a real cloud account — provider flows are
    fixture-driven with fake az / aws / gcloud / kubectl.

Full changelog: https://github.com/ymedlop/kuberoutectl/blob/main/CHANGELOG.md

Assets 15
Loading