ci: per-PR plugin version bumps force repeated base merges on every PR at the current merge rate - part 3 of 7 #10859

Activity

1. melodic-automation-lanes

   added the

   Task

   issue type on Oct 29, 2026
2. melodic-automation-lanes

   added a parent issue on Oct 29, 2026

   • ci: per-PR plugin version bumps force repeated base merges on every PR at the current merge rate #6006
3. melodic-automation-lanes

   marked this as blocked on Oct 29, 2026

   • ci: per-PR plugin version bumps force repeated base merges on every PR at the current merge rate - part 2 of 7 #10858
4. melodic-automation-lanes

   marked this as blocking on Oct 29, 2026

   • ci: per-PR plugin version bumps force repeated base merges on every PR at the current merge rate - part 4 of 7 #10860
5. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 29, 2026
6. github-actions commented on Oct 29, 2026

   

   github-actionsBot

   on Oct 29, 2026 – with GitHub Actions

   Last edited by melodic-automation-lanes

   Contributor

   More actions

   Proposed work class: work-class: scoped
   Basis: automated intake triage; the lanes App applied this class.

   Size: Small
   Complexity: Medium
   Uncertainty: Known
   Flags: none
   Blocked by: none

   Understood: this is part 3 of 7 of #6006. It asks for two CI changes. First, wire --check and --check-required into the changelog job, and --check-release into the release PR and merge_group. Second, make the release job check out full history, since release-plugins.sh orders fragments by commit and refuses to run in a shallow clone.

   The scope is clear from the done-when items. Sibling parts #10857, #10858, #10860, #10861, #10862 and #10863 are the other splits of the same parent, not duplicates.

   _{Automated triage, applied by the lanes App.}
7. github-actions

   added

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   and removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 29, 2026
8. melodic-automation-lanes

   added

   status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

   work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.A briefed fix or small feature; blast radius bounded by the brief, tests exist.

   on Oct 29, 2026
9. melodic-automation-lanes commented on Oct 29, 2026

   

   melodic-automation-lanesBot

   on Oct 29, 2026

   ContributorAuthor

   More actions

   Not admitted to the issue lane yet: blocker #10858 is not closed by a listed human or a merge.
10. melodic-automation-lanes

    added

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

    and removed

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

    on Oct 29, 2026
11. melodic-automation-lanes commented on Oct 29, 2026

    

    melodic-automation-lanesBot

    on Oct 29, 2026

    ContributorAuthor

    More actions

    The work-resolve-issue lane stopped partway through this issue and needs a person.

    Why, in the run's own words:

    already-done: both done-when items of ＃10859 are already on main at e12a3e3, so this run made no change. A person should confirm and close the issue as completed. (1) The changelog job in .github/workflows/pr-require-checks.yml runs scripts/check-changelog-fragments.sh --check (step changelog_fragments_check, line 1928) and --check-required (step changelog_fragments_required, lines 1948 and 1950, for both merge_group and pull_request). It runs --check-release on the release pull request against origin/$BASE_REF and in merge_group against merge_group.base_sha (step changelog_fragments_release, lines 1978 and 1980). All three outcomes feed the gate summary at lines 2134-2136. (2) The release build job in .github/workflows/release-publish-plugins.yml checks out main with fetch-depth: 0 (line 177), and a comment there gives the reason: release-plugins.sh orders fragments by commit and refuses a shallow clone. Any further edit here would land under /.github/workflows/**, which this lane cannot push.

    What the run says it did not do:

    • Could not identify which earlier PR landed this wiring: the lane checkout's history holds only one commit
    • tidy: skipped, there is no diff to tidy
    • review, build/test and lint: skipped, there is no diff

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40912191039

    To retry, remove needs-human and add agent-ready again.
12. kyle-sexton commented on Oct 29, 2026

    

    kyle-sexton

    on Oct 29, 2026

    Member

    More actions

    Closing as completed: the done-when is already on main. pr-require-checks.yml runs scripts/check-changelog-fragments.sh --check (:1932), --check-required 'HEAD^1' (:1952) and --check-release "$MERGE_GROUP_BASE_SHA" (:1982), and those outcomes feed the gate (:2138-2140); release-publish-plugins.yml checks out main with fetch-depth: 0 (:170-177). Checked against origin/main by a fresh-context verifier and again here.
13. kyle-sexton

    closed this as completedon Oct 29, 2026