ci: only run on branch pushes; drop bump-script emerge; repoint vendor tags #20

2026-09-20T19:26:15-05:00

azy5030 commented

2026-09-20 19:26:15 -05:00

CI trigger

ci.yaml used an unfiltered on: [push], which also fires for tag refs, including the gitea-runner-<ver>-vendor tags the bump script creates via the API. It is now filtered to branch pushes.

Bump script

scripts/bump-version.sh no longer runs pkgcheck / emerge / gitea-runner --version before pushing. The branch push triggers CI, which runs the same checks and, unlike the script's local copy of the distfiles, fetches the real release asset through the Manifest. The generated PR body now asks for green CI instead of claiming the build passed in the bump job.

Behavioural change: a broken upstream release now surfaces as a bump PR with red CI rather than a failed scheduled run. Retrying means closing that PR and deleting its branch, since the script exits early when the bump branch exists.

Vendor tag repointing

New vendor-tags.yaml workflow on pushes to master touching dev-util/**. The vendor release is created before the bump commit exists, and PRs are squash-merged, so its tag pointed at an arbitrary master commit (most current tags sit on the 2.0.1 bump). The job force-updates each vendor tag whose ebuild is in the tree to the master commit that added that ebuild. It only updates tags, never deletes them: deleting a release's tag makes Gitea delete the release and its assets, which would break SRC_URI.

First run after merge will move the 3.3.0 and 3.3.1 tags. Tags for versions no longer in the tree are left alone.

🤖 Generated with Claude Code

## CI trigger `ci.yaml` used an unfiltered `on: [push]`, which also fires for tag refs, including the `gitea-runner-<ver>-vendor` tags the bump script creates via the API. It is now filtered to branch pushes. ## Bump script `scripts/bump-version.sh` no longer runs `pkgcheck` / `emerge` / `gitea-runner --version` before pushing. The branch push triggers CI, which runs the same checks and, unlike the script's local copy of the distfiles, fetches the real release asset through the Manifest. The generated PR body now asks for green CI instead of claiming the build passed in the bump job. Behavioural change: a broken upstream release now surfaces as a bump PR with red CI rather than a failed scheduled run. Retrying means closing that PR and deleting its branch, since the script exits early when the bump branch exists. ## Vendor tag repointing New `vendor-tags.yaml` workflow on pushes to `master` touching `dev-util/**`. The vendor release is created before the bump commit exists, and PRs are squash-merged, so its tag pointed at an arbitrary `master` commit (most current tags sit on the 2.0.1 bump). The job force-updates each vendor tag whose ebuild is in the tree to the `master` commit that added that ebuild. It only updates tags, never deletes them: deleting a release's tag makes Gitea delete the release and its assets, which would break `SRC_URI`. First run after merge will move the 3.3.0 and 3.3.1 tags. Tags for versions no longer in the tree are left alone. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

azy5030 added 1 commit 2026-09-20 19:26:16 -05:00

ci: only run on branch pushes; drop bump-script emerge; repoint vendor tags

CI / lint (push) Successful in 58s

Details

CI / build (push) Successful in 11m54s

Details

c9a31ba468

- ci.yaml: filter the push trigger to branches. An unfiltered `push` also
  fired for every tag ref, including the vendor-release tags the bump script
  creates via the API.
- bump-version.sh: remove the pkgcheck/emerge/--version validation before
  push. The branch push triggers CI, which runs the same checks and, unlike
  the script's local copy, fetches the real release asset. The PR body now
  asks for green CI instead of claiming the build passed in the bump job.
- vendor-tags.yaml: new workflow on pushes to master touching dev-util/**.
  The vendor release is created before the bump commit exists (and PRs are
  squash-merged), so its tag pointed at an arbitrary master commit. This
  force-updates each vendor tag whose ebuild is in the tree to the master
  commit that added that ebuild. Tags are only ever updated, never deleted,
  since deleting a release's tag deletes the release and its assets.
- CLAUDE.md: document both changes.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

azy5030 scheduled this pull request to auto merge when all checks succeed 2026-09-20 19:27:23 -05:00

azy5030 merged commit c9a31ba468 into master

2026-09-20 19:37:29 -05:00

azy5030 deleted branch fix-ci-stuff

2026-09-20 19:37:29 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: azy5030/azy5030-overlay#20