shipmate

Changelog

What changed for operators in each release, newest first. The images and the Helm chart of a release share its version number.

Every release is signed

Release images are built and published by the project’s release workflow, which signs each one without a long-lived key. You can check that before you run it.

Signature
Keyless cosign signatures (Sigstore), made by the release workflow with its GitHub identity, on each image’s digest.
Inside the image
An SBOM and build provenance, attached by the build.
Tags
One tag per version, such as 0.2.10. There is no :latest: pin a version, or better, its digest.
Platform
linux/amd64
Check a release’s signature
cosign verify ghcr.io/roundbeat-ai/shipmate:<X.Y.Z> \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --certificate-identity https://github.com/RoundBeat-Ai/shipmate/.github/workflows/release-please.yml@refs/heads/main

The images are private, so you’ll need the registry access we set up with your team. Releases and upgrades in the docs shows how to read the SBOM and upgrade.

Releases

A curated summary. Fixes to the website and to our own release tooling are left out.

  1. 0.2.10

    • The agent’s browser starts by itself when it’s needed, from Shipmate’s own slim image, and pages load in English by default.
  2. 0.2.9

    • New agents start out knowing how to take useful screenshots, and never to put a secret on screen.
    • The agent is told it can post images and use its browser, and it closes the browser when it’s done.
    • Shipyard, the self-hosted control plane, shows the running release in its footer and where to find each chat platform’s user IDs.
  3. 0.2.8

    • A browser for each agent, which scales to zero when it isn’t in use, and screenshots posted straight into the thread. Turn it on with browser.enabled in the Helm chart, or one switch in Shipyard.
    • browser.egress: public keeps the browser off private and link-local addresses.
    • The browser’s token stays off the command line, out of chat and out of upload filenames.
    • Images posted to Microsoft Teams stay within its inline limits, and failed uploads are counted.
  4. 0.2.7

    • Only stuck turns are stopped. A long turn shows its progress in the thread, and a stopped turn keeps the work it had done. Retries and status updates no longer reset the idle clock.
    • In Shipyard’s setup wizard, the shipmate you chose walks beside you and helps at each step.
  5. 0.2.6

    • A crew of shipmates: choose your agent’s look in Shipyard, each with its own faces, and watch launch day as the agent is commissioned.
  6. 0.2.5

    • Shipyard takes a Claude subscription for an agent only you talk to, and the agent stays personal after launch. Shared agents use an API key or a cloud provider.
    • A model list, and help finding each token.
    • One chat platform per agent, for now.
  7. 0.2.4

    • Shipyard: a self-hosted control plane that commissions each agent in a namespace of its own, with a web interface.
    • The console, rebuilt.
    • secretFiles in the Helm chart mounts secret files, such as an SSH key or cloud credentials, read-only.
  8. 0.2.3

    • Discord: alerts from bots and webhooks, channels open to anyone, and an allowlist for direct messages.
    • The agent can post to channels you allow, besides the conversation it’s answering.
    • The image ships a compiled gateway instead of source.
    • Deploys dispatched through GitHub Actions count as changes, so verification follows them.
    • Status replies are easier to scan, and scheduled checks get their whole entry.
    • Discord no longer asks for the Server Members intent.
  9. 0.2.2

    • Memory on a volume of its own: what’s true now, the state of each system, runbooks, incident write-ups and a monthly log.
    • The agent runs as root in its own container and improves itself: the tools and setup it adds live on its workspace volume and come back after a restart.
    • Shipmate’s own programs and config are protected by their real paths.
  10. 0.2.1

    • Every verdict in the agent’s replies carries its full mark.