Repository navigation
Releases
Releases · shipyard/shipyard-plugins
shipyard-hosted v0.2.1
First-run onboarding, from SE feedback on Kiro's Try power (SHIP-658, #10).
- On activation: the skill checks the connection, runs the preflight, looks for a Compose file, then makes one offer: "Want me to put this repo on Shipyard?"
- Two yeses to add an app: one proposal covers the repo (
gh repo createif there's no GitHub remote), the files to commit by name, the Compose file, the branch and the push. Then one confirm beforecreate_application. - Never committed:
.env, keys, Terraform state, build output, dependencies, and files over 50 MB. - Env values: proposes non-secret values from
.env.example, Compose defaults or the obvious choice; never proposes secrets. - No org question: single-org users already have their org picked at sign-in; the confirm shows it.
- README for the hosted plugin (
hosted/README.md).
Tested end to end in Kiro.
shipyard-hosted v0.2.0
The hosted plugin's onboarding release (SHIP-658, #9). A new user can go from no account to a running first environment, including repos that have no Docker Compose file.
- Getting started: how to connect in Kiro, Claude Code and Codex; signing up from the sign-in page; confirming the org picked at sign-in before adding an app. The skill never asks for a token.
- Compose guide (
skills/shipyard/references/compose.md): finds an existing file first, analyzes the repo, and writes a compose file with Shipyard labels and variables. It checks the file with Docker Compose without loading.env, keeps literal secrets out of committed files, and commits and pushes only the files it showed, with the user's yes. - Kiro: install from
https://github.com/shipyard/shipyard-plugins/tree/main/hosted. Signing in and reading environments have been tested in Kiro. - A new CI check fails if a skill names a
references/file that doesn't exist.