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
🐛 - Bugbot recommends SHA replacements against the consumer complete release tag policy #966
Bugbot recommends replacing the consumer's reviewed full release references with commit SHAs even though the consumer explicitly requires complete release tags in installed workflow references. The same-head source documentation records this policy. Review fixes should account for the repository's declared dependency-reference policy and support an explicitly documented maintainer disposition when the requested alternative conflicts with that policy.
The underlying limitation is real. GitHub's action lockfile currently excludes job-level reusable workflow calls. This report concerns the proposed fix and the handling of the accepted policy, including keeping that limitation visible during review. The separate finding about ordinary action steps missing from the action lockfile has been accepted and is being corrected through ha-ui #34 and the open Domus workflow maintenance PR.
Reproducing the issue
Review ha-ui promotion PR 🐛 - Missing branching emoji #33 at 42abe4563a37ee4c5847dbf56ebe4b9a1d3fef18 against master 9b71355ffbf162dbc76c48e02546acaf8948772f.
Read the complete-version requirement in docs/storybook.md and the architecture assertion requiring full release tags for installed external references.
Inspect run 44382822011 and finding copilot_issue_comment.yml:10:mutable-reusable-workflow. The suggested fix replaces both reviewed v3.10.13 reusable calls with SHAs.
The consumer retains the complete released v3.10.13 references, previously verified to resolve to ace49e4a7ce0f6a007fef5d11479eb9b7a5846e3. Maintainer disposition should preserve that declared decision and disclose the lockfile boundary.
The consumer workflow maintenance is tracked in ha-ui #31 and Domus #134. The consumer repositories use a shared persistent self-hosted pool for reviewed internal branches, with GitHub-hosted OIDC publication. The maintainer has authorized continuation past diagnosed Copilot review conflicts after recording them here. Copilot source work remains with its owning agent.
changed the title [-]Bugbot recommends SHA replacements against the consumer complete release tag policy[/-][+]🐛 - Bugbot recommends SHA replacements against the consumer complete release tag policy[/+]on Nov 18, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try /copilot help to see the available commands, or mention @vypbot with your question.
Activity
[-]Bugbot recommends SHA replacements against the consumer complete release tag policy[/-][+]🐛 - Bugbot recommends SHA replacements against the consumer complete release tag policy[/+]vypbot commentedon Nov 18, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.