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
[quality] push-repacked-dist cannot mint its App token: Dependabot secrets REPACK_APP_ID / REPACK_APP_PRIVATE_KEY are not configured #452
On dependabot branches the step reads Dependabot secrets, and those two have never been configured. Latest evidence, PR #440 (js-yaml 5.4.2 → 5.4.3, run 38068101038):
repack-dist succeeded with changed=true and uploaded the artifact — the job pair works.
push-repacked-dist failed at step 1: "The 'client-id' (or deprecated 'app-id') input must be set to a non-empty string. If using a secret or variable, ensure it is available in this workflow context."
This was previously recorded only as a folded comment on #422, which was closed on 2026-10-11 without the secrets being added, so nothing open tracks it now. Every future dependabot bump of an ncc-bundled runtime dependency (js-yaml, @actions/*, …) will reproduce it.
Recommendation
No repository change can fix this; it needs a maintainer with repo-settings access (needs-human: Dependabot secrets are not writable by any agent or workflow). Please choose one:
(preferred) Add REPACK_APP_ID and REPACK_APP_PRIVATE_KEY under Settings → Secrets and variables → Dependabot (same values as the Actions-scoped App used by prow-bot.yml, or a dedicated App with contents: write on this repo), then re-run build-test on chore(deps): bump js-yaml from 5.4.2 to 5.4.3 in the production-dependencies group #440 to confirm push-repacked-dist pushes the repacked dist/.
This is NOT DONE and appears human-only: the issue body identifies missing Dependabot-scoped REPACK_APP_ID / REPACK_APP_PRIVATE_KEY secrets under repo settings. No repository PR can set those secrets. I found no merged fix PR and no deployment evidence to close this. A maintainer with settings access needs to add the secrets (or decide to remove the job) and rerun a bundled-dependency Dependabot PR to confirm.
Activity
github-actions commentedon Oct 11, 2026
Please add a kind label with
/kind failing-testor/kind cleanup.hivecommons-hive commentedon Oct 11, 2026
What to reply
/hive approve: go with the recommendation/hive decision <your instructions>: go ahead, following your instructions/hive help: show these againIf this issue is waiting only for reporter confirmation after a merged fix, the reporter or a maintainer can reply
/fixedinstead.Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.
clubanderson commentedon Oct 14, 2026
Disposition from Hive onboarding review (hivecommons/hive#9846): leaving this open.
This is NOT DONE and appears human-only: the issue body identifies missing Dependabot-scoped
REPACK_APP_ID/REPACK_APP_PRIVATE_KEYsecrets under repo settings. No repository PR can set those secrets. I found no merged fix PR and no deployment evidence to close this. A maintainer with settings access needs to add the secrets (or decide to remove the job) and rerun a bundled-dependency Dependabot PR to confirm.ci(test): drop the Dependabot dist/ repack jobs (cncf#489)