Upgrade tapster

Your hub’s workflow pins the exact tapster commit that wrote it. A new tapster release changes nothing in your hub until you move it there yourself. To hear about new releases, open tapster on GitHub and choose Watch, Custom, Releases.

With the tapster service, the setup page offers each new release and then the hub’s update, each with one click. The steps below do the same from a terminal.

Move the hub

In a clone of your hub:

git pull
bunx @doguyilmaz/tapster@<version> init --workflow
git diff

init --workflow rewrites .github/workflows/tapster.yml for that version and pins it by commit. Read the diff, then commit and push it:

git commit -am "Move the hub to tapster <version>"
git push

Note

Add --every <minutes> to change how often the hub looks for drafts in the same step.

If the hub has a doorbell

The doorbell runs its own copy of tapster’s Worker. Move it to the same version and schedule. tapster asks for a new private key of the doorbell App and a Cloudflare token:

bunx @doguyilmaz/tapster@<version> init --rotate doorbell

Check it

bunx @doguyilmaz/tapster@<version> doctor

You should see

Every check reports ok.

Coming from a version before 1.0

Since 1.0 the hub refuses a project until its branches and tags are protected. Run tapster add once in a clone of each project. It only adds what is missing and keeps what an earlier --auto-tag or --allow-dependabot opened.