Skip to content

Spinnaker changelog

io.github.geiserx/spinnaker-mcp

6 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • server.json 1 field changed
    version
    0.4.0 0.4.1

  • server.json 5 fields changed
    env_vars
    GATE_URL, GATE_TOKEN, GATE_USER, GATE_PASS GATE_URL, GATE_TOKEN, GATE_USER, GATE_PASS, GATE_COOKIE, GATE_COOKIE_FILE, GATE_CERT_FILE, GATE_KEY_FILE, GATE_INSECURE, TOOLSETS
    icon_url
    — https://raw.githubusercontent.com/GeiserX/spinnaker-mcp/main/docs/images/icon.svg
    title
    spinnaker mcp Spinnaker
    version
    0.3.7 0.4.0
    website_url
    — https://geiserx.github.io/spinnaker-mcp/

  • server.json 1 field changed
    version
    0.3.6 0.3.7

  • server.json 1 field changed
    version
    0.3.5 0.3.6

  • AGENTS.md 1 field changed
    file
    absent published

    https://raw.githubusercontent.com/geiserx/spinnaker-mcp/HEAD/AGENTS.md

    + # Agent Instructions+ This project uses **bd** (beads) for issue tracking. Run `bd prime` for full workflow context.+ > **Architecture in one line:** Issues live in a local Dolt database+ > (`.beads/dolt/`); cross-machine sync uses `bd dolt push/pull` (a+ > git-compatible protocol), stored under `refs/dolt/data` on your git+ > remote — separate from `refs/heads/*` where your code lives.+ > `.beads/issues.jsonl` is a passive export, not the wire protocol.+ >+ > See [SYNC_CONCEPTS.md](https://github.com/gastownhall/beads/blob/main/docs/SYNC_CONCEPTS.md)+ > for the one-screen overview and anti-patterns (don't treat JSONL as the+ > source of truth; don't `bd import` during normal operation; don't+ > reach for third-party Dolt hosting before trying the default).+ ## Quick Reference+ ```bash+ bd ready              # Find available work+ bd show <id>          # View issue details+ bd update <id> --claim  # Claim work atomically+ bd close <id>         # Complete work+ bd dolt push          # Push beads data to remote+ ```+ ## Non-Interactive Shell Commands+ **ALWAYS use non-interactive flags** with file operations to avoid hanging on confirmation prompts.+ Shell commands like `cp`, `mv`, and `rm` may be aliased to include `-i` (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.+ **Use these forms instead:**+ ```bash+ # Force overwrite without prompting+ cp -f source dest           # NOT: cp source dest+ mv -f source dest           # NOT: mv source dest+ rm -f file                  # NOT: rm file+ # For recursive operations+ rm -rf directory            # NOT: rm -r directory+ cp -rf source dest          # NOT: cp -r source dest+ ```+ **Other commands that may prompt:**+ - `scp` - use `-o BatchMode=yes` for non-interactive+ - `ssh` - use `-o BatchMode=yes` to fail instead of prompting+ - `apt-get` - use `-y` flag+ - `brew` - use `HOMEBREW_NO_AUTO_UPDATE=1` env var+ <!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:970c3bf2 -->+ ## Beads Issue Tracker

    Showing the first 40 of each.

  • server.json 1 field changed
    version
    0.3.2 0.3.5