Self-dogfood: add `.forgejo/workflows/fragment-check.yml` to release-toolkit (post-v0.20.0-cut) #281

New issue

Closed

opened 2026-07-02 10:12:03 +02:00 by quartermaster · 0 comments

quartermaster commented

2026-07-02 10:12:03 +02:00

Owner

Why

Deferred from release-toolkit#271 AC #5 during the #278 fix-up cycle. The dogfood wrapper was included in PR #278's initial version but had to be dropped because:

Pinning .forgejo/workflows/fragment-check.yml to the sibling uses:@v0.20.0-rc.2 would fail resolution — the reusable-changelog-fragment-check.yml doesn't exist at that tag (introduced in this PR).
Pinning to @main would break check-self-bootstrap.sh's single-ref-alignment invariant (all wrappers must pin the SAME ref).

The clean resolution is to wire the toolkit-self dogfood after v0.20.0-stable cuts (which is held on PR #278 landing per Bosun 2026-07-02). At that point the sibling wrappers move to @v0.20.0, and the new fragment-check wrapper can pin to the same tag which will then contain the reusable.

What

Add .forgejo/workflows/fragment-check.yml mirroring the sibling manifest-check.yml pattern:

name: fragment-check
on:
  pull_request:
    branches: [main]
    paths: ['changelog.d/**']

jobs:
  check:
    uses: frankenbit/release-toolkit/.forgejo/workflows/reusable-changelog-fragment-check.yml@v0.20.0
    with:
      runs_on:     go

Version pin should match whatever the sibling wrappers pin at the time (currently v0.20.0-rc.2; post-cut becomes v0.20.0).

Acceptance criteria

.forgejo/workflows/fragment-check.yml present, pinned to the current sibling ref.
tests/workflows.bats regains a guard asserting the dogfood wrapper exists + wires the reusable + carries changelog.d paths filter (the version I authored in #278 pre-cleanup is preserved in the commit history).
check-self-bootstrap.sh passes on the resulting main (all three wrappers aligned).

Refs

Parent: release-toolkit#271
Deferring PR: release-toolkit#278 fix-up cycle 2026-07-02
Substrate anchor: Surveyor review on PR #278 flagged the bake-list gap; toolkit-self dogfood dropped as tangential to the must-fix

Blocked-on

release-toolkit v0.20.0-stable cut.

## Why Deferred from release-toolkit#271 AC #5 during the #278 fix-up cycle. The dogfood wrapper was included in PR #278's initial version but had to be dropped because: - Pinning `.forgejo/workflows/fragment-check.yml` to the sibling `uses:@v0.20.0-rc.2` would fail resolution — the `reusable-changelog-fragment-check.yml` doesn't exist at that tag (introduced in this PR). - Pinning to `@main` would break `check-self-bootstrap.sh`'s single-ref-alignment invariant (all wrappers must pin the SAME ref). The clean resolution is to wire the toolkit-self dogfood **after** `v0.20.0-stable` cuts (which is held on PR #278 landing per Bosun 2026-07-02). At that point the sibling wrappers move to `@v0.20.0`, and the new fragment-check wrapper can pin to the same tag which will then contain the reusable. ## What Add `.forgejo/workflows/fragment-check.yml` mirroring the sibling `manifest-check.yml` pattern: ```yaml name: fragment-check on: pull_request: branches: [main] paths: ['changelog.d/**'] jobs: check: uses: frankenbit/release-toolkit/.forgejo/workflows/reusable-changelog-fragment-check.yml@v0.20.0 with: runs_on: go ``` Version pin should match whatever the sibling wrappers pin at the time (currently `v0.20.0-rc.2`; post-cut becomes `v0.20.0`). ## Acceptance criteria 1. `.forgejo/workflows/fragment-check.yml` present, pinned to the current sibling ref. 2. `tests/workflows.bats` regains a guard asserting the dogfood wrapper exists + wires the reusable + carries `changelog.d` paths filter (the version I authored in #278 pre-cleanup is preserved in the commit history). 3. `check-self-bootstrap.sh` passes on the resulting main (all three wrappers aligned). ## Refs - Parent: release-toolkit#271 - Deferring PR: release-toolkit#278 fix-up cycle 2026-07-02 - Substrate anchor: Surveyor review on PR #278 flagged the bake-list gap; toolkit-self dogfood dropped as tangential to the must-fix ## Blocked-on release-toolkit `v0.20.0-stable` cut.