Skip to content

ci: bump ci.yml action pin, allow bot PR reviews, fix release-prepare#60

Merged
tbjers merged 7 commits into
release/v0.4.0from
ci/release-prepare-bump-ci-pin
Jul 7, 2026
Merged

ci: bump ci.yml action pin, allow bot PR reviews, fix release-prepare#60
tbjers merged 7 commits into
release/v0.4.0from
ci/release-prepare-bump-ci-pin

Conversation

@tbjers

@tbjers tbjers commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Retargeted onto release/v0.4.0 (#59) so v0.4.0 tags correctly instead of carrying a stale action pin.

  • release-prepare.yml now also bumps .github/workflows/ci.yml's two .../report@vX.Y.Z pins (previously only the README pins were updated), and gained workflows: write permission (the verified-commit GraphQL call rejects writes under .github/workflows/ without it).
  • Manually bumped ci.yml's two pins from @v0.3.0 to @v0.4.0 directly, since release/v0.4.0 was branched before this fix existed — category support shipped in the action but ci.yml still referenced the pre-category @v0.3.0.
  • Added allowed_bots: "dependabot[bot],copilot[bot]" to claude-code-review.yml so Dependabot/Copilot PRs get reviewed instead of skipped.

Test plan

  • Dry-ran the sed pattern used by release-prepare.yml against a copy of ci.yml — both pins bump correctly, no unintended matches.
  • ci.yml now pins @v0.4.0 directly in this branch.
  • Next real exercise of the automated bump is the following release (v0.4.0 already has this baked in manually).

🤖 Generated with Claude Code

The release-prepare workflow updated README action-usage pins but not
ci.yml's own two `.../report@vX.Y.Z` references, so this repo's CI kept
pinning the report action to a stale version after every release (as
just happened: category support shipped in the action, but ci.yml still
referenced @v0.3.0, which predates it). Requires workflows: write since
the release commit now touches a file under .github/workflows/.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 7, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
demo-coveragetracker-dev c52caf3 Commit Preview URL

Branch Preview URL
Jul 07 2026, 02:35 AM

- Manually bump ci.yml's two report-action pins from @v0.3.0 to @v0.4.0
  ahead of the v0.4.0 tag, since release/v0.4.0 was already branched
  before the release-prepare.yml fix in this PR existed to do it
  automatically.
- Add allowed_bots to claude-code-review.yml so Dependabot and Copilot
  PRs get reviewed instead of skipped.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@tbjers
tbjers changed the base branch from main to release/v0.4.0 July 7, 2026 02:01
@tbjers tbjers changed the title ci: bump ci.yml's action pin during release prep ci: bump ci.yml action pin, allow bot PR reviews, fix release-prepare Jul 7, 2026
tbjers and others added 5 commits July 6, 2026 22:04
release-prepare.yml (and the manual bump in this PR) pins ci.yml's
report-action reference to the version being released before its tag
exists, so any PR against a release/vX.Y.Z branch fails at action
resolution. Skip the Report coverage step in that case; it still runs
normally on PRs against main and on push (post-merge, once the tag is
live).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Step-level `if:` doesn't work here — GitHub Actions resolves every
`uses:` reference in a job during job setup regardless of each step's
condition, so the just-bumped-but-not-yet-tagged report-action pin
still fails resolution even when the step using it is skipped.
Excluding release/** as a pull_request base branch prevents the
workflow from starting at all, which is the only way to avoid it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Point both Report coverage steps at ./.github/actions/report instead of
a pinned CoverageTracker/coverage-tracker/.../report@vX.Y.Z tag. This
repo dogfoods its own action, so it should run the exact code on the
current branch rather than a released version — and a local path never
needs resolving a tag/branch at all, which permanently removes the
catch-22 where release-prep bumped this pin ahead of the tag existing.

Reverts the now-unnecessary release-prepare.yml changes (ci.yml pin
bumping, workflows: write) since there's no longer a pin here to bump.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@tbjers
tbjers merged commit 8a3d09a into release/v0.4.0 Jul 7, 2026
10 checks passed
@tbjers
tbjers deleted the ci/release-prepare-bump-ci-pin branch July 7, 2026 02:41
tbjers added a commit that referenced this pull request Jul 7, 2026
* chore(release): v0.4.0

* ci: reference the report action by local path, not a version pin (#60)

* ci: reference the report action by local path, not a version pin

Point both Report coverage steps at ./.github/actions/report instead of
a pinned CoverageTracker/coverage-tracker/.../report@vX.Y.Z tag. This
repo dogfoods its own action, so it should run the exact code on the
current branch rather than a released version — and a local path never
needs resolving a tag/branch at all, which permanently removes the
catch-22 where release-prep bumped this pin ahead of the tag existing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Torgny Bjers <torgny@bjers.org>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant