v1.4.7

One feature, one cosmetic fix. No breaking changes; nothing runs differently until you create a cron.

Scheduled rebuilds: cron named rebuild

rake woodpecker now generates a rebuild-<version>-<variant> step per image, triggered by a Woodpecker cron named rebuild. It runs after render (so each run gets a fresh build ID) and does rake build test scan tag push with VERSION from metadata.yaml. Base-image and package fixes ship without a commit or a new git tag.

The steps filter on the cron name, so they are inert until you add the cron:

woodpecker-cli repo cron add --repo ORG/REPO --name rebuild --branch main --schedule '0 11 * * *'

Schedules are standard 5-field cron, UTC. Each run publishes a new b<id> tag and moves floating tags (latest, version tags, git_sha tags) to the rebuilt image.

No more YAML anchors in the generated pipeline

The generated .woodpecker/build.yaml no longer contains &1/*1 aliases for repeated when/environment blocks.

Note for consuming repos

Run rake update && rake woodpecker and commit the regenerated .woodpecker/build.yaml. If rake update pulls a stale copy from the CDN, use CRUCIBLE_REF=v1.4.7 rake install.