chadtmiller.com/knotless

Switch repository

Loading…

What changes

deploy.yml and release.yml call knotless by its grouped names: repo refs, release list, release publish and tag create, in place of refs, releases, publish and tag.

Why

The old names work only until the follow-up that removes them. Both workflows can move now. deploy.yml runs the image already on the host, which has known both names since the grouping deployed (ab61a920). release.yml builds knotless from the commit it runs.

The shared steps in chadtmiller.com/steps (site, wait-for-checks) still use the old names. Where an image has no knotless, they install the newest release, 0.9.0, which knows only the old names. They move once a release with the grouped names is out, and the old names go after that.

How it was checked

No other old name is left in deploy/, harness/, the Justfile or .knotless/. deploy and release run on main once this lands, and that run is the check.

Changeset: none

🤖 Generated with Claude Code

This renames the five old command calls in deploy.yml and release.yml to their grouped names: repo refs, release list (twice), release publish (twice) and tag create. I checked the diff against the base branch. Every old knotless refs, releases, publish and tag call in .knotless/ is covered, and the arguments are unchanged. The only other uses of the old names are in CHANGELOG.md and docs, which describe past releases. Your plan makes sense: deploy.yml uses the image already on the host, and release.yml builds knotless from the commit it runs. The shared steps stay on the old names until a release with the grouped names is out. I did not run the workflows or confirm that the host image knows the grouped names. I relied on the PR body for that, and the run on main will show it.