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

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 blocking on Oct 29, 2026

   • ci: per-PR plugin version bumps force repeated base merges on every PR at the current merge rate - part 3 of 7 #10859
4. 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
5. 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 2 of 7 of #6006, split at intake. It asks for two changes to the changelog parity check, with no plugin opted in yet. First, --check-bump should count a consumed .changes/ fragment as the change, so a release PR no longer fails BUMP WITHOUT CHANGE. Second, a hand version bump or CHANGELOG heading on a fragment-mode plugin should be rejected in any PR other than the release PR. The done-when names a scratch test that currently passes when it should fail. Nothing is missing. The sibling parts (#10857, #10859 to #10863) cover different slices of #6006, so none is a duplicate.

   _{Automated triage, applied by the lanes App.}
6. 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
7. 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.

   admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.Admitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.

   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

   admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.Admitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.

   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
8. 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 ＃10858 are already on main at abb359b, so there is nothing to change. (1) scripts/check-changelog-parity.sh --check-bump counts a fragment the change set deletes under .changes/<name>/ as the change (consumed_fragment, lines 624-635 and 925), so a release PR no longer fails BUMP WITHOUT CHANGE. (2) On any PR other than the release PR, --check-bump fails a version move or an added CHANGELOG heading on a fragment-mode plugin (FRAGMENT-MODE RELEASE, lines 829-848). check-changelog-fragments.sh --check-required now exempts the CHANGELOG.md edit and the version-only plugin.json edit only on the release PR (lines 145-156). A person should check this and close the issue as already done.

   What the run says it did not do:

   • scripts/check-changelog-parity.test.sh and scripts/check-changelog-fragments.test.sh were not run: this lane can run only the named wrappers. I read the tests but did not execute them.
   • tidy, review, verify and the PR prep were skipped: the run made no change, so there is nothing to tidy or review.

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

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

   

   kyle-sexton

   on Oct 29, 2026

   Member

   More actions

   Already done on main, verified: scripts/check-changelog-parity.sh counts a consumed fragment as the change (:536, :633) and fails a fragment-mode release on a non-release PR (:804-840); check-changelog-fragments.sh exempts the CHANGELOG/version edit only on the release PR (:145-156). check-changelog-parity.test.sh PASS=127 FAIL=0, check-changelog-fragments.test.sh PASS=75 FAIL=0.
10. kyle-sexton

    closed this as completedon Oct 29, 2026
11. kyle-sexton

    added a commit that references this issue on Oct 29, 2026

    fix(pr-pipeline): close already-done issues only on evidence tied to …

    ...

    258fd3a