You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: per-PR plugin version bumps force repeated base merges on every PR at the current merge rate - part 1 of 7 #10857
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Medium
Uncertainty: Unknown
Flags: none
Blocked by: none
Understood: this is part 1 of 7 of #6006, split at intake. Its single done-when item is to run the version-omission probe (ADR, Resolved decisions 5) before phase 2 of removing per-PR plugin version bumps.
Only that one item is stated. The outcome depends on the probe's result, which only an experiment can show. Parts 2–7 (#10858 onward in this series) are sibling slices of the same parent, not duplicates.
Not admitted to the issue lane: Uncertainty unknown is not one of known, knowable. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).
melodic-automation-lanes commented on Oct 29, 2026
Closing as not planned (superseded). The version-omission probe was a gate to run before phase 2 of ADR 0048 (Resolved decisions 5). Phases 2-5 have since shipped: ADR 0048 records every plugin in fragment mode, the dedicated release App runs release-publish-plugins.yml (vars.PLUGIN_RELEASE_APP_CLIENT_ID), and chore(release) PRs merge on schedule (latest #11303). The probe now informs only the deferred 'Omit version' alternative, which keeps its own recheck trigger in the ADR: recheck when the loading page states which commit the SHA version comes from. Parent #6006 is closed as completed.
Activity
github-actions commentedon Oct 29, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Medium
Uncertainty: Unknown
Flags: none
Blocked by: none
Understood: this is part 1 of 7 of #6006, split at intake. Its single done-when item is to run the version-omission probe (ADR, Resolved decisions 5) before phase 2 of removing per-PR plugin version bumps.
Only that one item is stated. The outcome depends on the probe's result, which only an experiment can show. Parts 2–7 (#10858 onward in this series) are sibling slices of the same parent, not duplicates.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 29, 2026
Not admitted to the issue lane: Uncertainty unknown is not one of known, knowable. Admission takes the issue once each of those is met, when intake triages it again (
.github/actions/resolve-config/admission-rules.json).melodic-automation-lanes commentedon Oct 29, 2026
The latest triage verdict holds nothing: admission moved the issue to
status: confirmed; its comment says why.kyle-sexton commentedon Oct 30, 2026
Closing as not planned (superseded). The version-omission probe was a gate to run before phase 2 of ADR 0048 (Resolved decisions 5). Phases 2-5 have since shipped: ADR 0048 records every plugin in fragment mode, the dedicated release App runs release-publish-plugins.yml (vars.PLUGIN_RELEASE_APP_CLIENT_ID), and chore(release) PRs merge on schedule (latest #11303). The probe now informs only the deferred 'Omit version' alternative, which keeps its own recheck trigger in the ADR: recheck when the loading page states which commit the SHA version comes from. Parent #6006 is closed as completed.