tim/hass-mcp
Watch
1
0
Fork
You've already forked hass-mcp
 0
Code Issues Pull requests Projects Releases 3 Packages Wiki Activity Actions

ci: fix auto-tag trigger and switch to gha cache #4

Merged
timstoop merged 1 commit from develop into main 2026-07-22 08:49:49 +00:00
Conversation 0 Commits 1 Files changed 2 -5
timstoop commented 2026-07-22 08:42:55 +00:00 (Migrated from codeberg.org)
Copy link

Summary

PR #3 merged and the auto-tag job did run (created v0.4.0), but that tag push never triggered docker.yml. Root cause: the job pushed the tag using the default Actions token, and Forgejo/GitHub Actions intentionally don't let pushes made with that token trigger other workflows (loop prevention).

  • auto-tag.yml: check out with token: ${{ secrets.CODEBERG_TOKEN }} (same secret already used elsewhere in docker.yml) so the tag push is a real authenticated push and does trigger downstream workflows.
  • docker.yml: switch cache from the Codeberg registry (type=registry, which was intermittently failing blob commits) to type=gha now that the runner supports it, and restore mode=max — full builder-stage caching, without touching the registry's unreliable path.

Note

v0.4.0 already exists as a tag (from PR #3) but was never built/released. After this merges, I'll re-push that tag using my own credentials so it triggers docker.yml properly and completes the pending 0.4.0 release — that also validates both fixes at once.

Test plan

  • YAML validated locally (pre-commit run check-yaml)
  • After merge + tag re-push: docker.yml runs, cache pushes to gha (no registry blob errors), release is created
## Summary PR #3 merged and the auto-tag job did run (created `v0.4.0`), but that tag push never triggered `docker.yml`. Root cause: the job pushed the tag using the default Actions token, and Forgejo/GitHub Actions intentionally don't let pushes made with that token trigger other workflows (loop prevention). - `auto-tag.yml`: check out with `token: ${{ secrets.CODEBERG_TOKEN }}` (same secret already used elsewhere in `docker.yml`) so the tag push is a real authenticated push and does trigger downstream workflows. - `docker.yml`: switch cache from the Codeberg registry (`type=registry`, which was intermittently failing blob commits) to `type=gha` now that the runner supports it, and restore `mode=max` — full builder-stage caching, without touching the registry's unreliable path. ## Note `v0.4.0` already exists as a tag (from PR #3) but was never built/released. After this merges, I'll re-push that tag using my own credentials so it triggers `docker.yml` properly and completes the pending 0.4.0 release — that also validates both fixes at once. ## Test plan - [x] YAML validated locally (`pre-commit run check-yaml`) - [ ] After merge + tag re-push: `docker.yml` runs, cache pushes to gha (no registry blob errors), release is created
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
tim/hass-mcp!4
No description provided.