actions/create-github-app-token@v3 deprecated its app-id input in favour of client-id (deprecationMessage: "Use 'client-id' instead." in its action.yml). .github/workflows/sibling-dependency-update.yml's own workflow_call.inputs.app-id presumably passes straight through to that action internally, so every caller (novus-power/hive included) sees the deprecation warning on each run.
Note client-id and app-id are genuinely different values (a GitHub App has both a numeric App ID and a separate Client ID string, e.g. Iv23li...), so this isn't a mechanical rename of the input name alone -- callers passing a hardcoded numeric app-id will need to switch to their app's actual client-id value once this workflow's own input changes.
actions/create-github-app-token@v3 deprecated its
app-idinput in favour ofclient-id(deprecationMessage: "Use 'client-id' instead."in its action.yml)..github/workflows/sibling-dependency-update.yml's ownworkflow_call.inputs.app-idpresumably passes straight through to that action internally, so every caller (novus-power/hive included) sees the deprecation warning on each run.Note client-id and app-id are genuinely different values (a GitHub App has both a numeric App ID and a separate Client ID string, e.g.
Iv23li...), so this isn't a mechanical rename of the input name alone -- callers passing a hardcoded numeric app-id will need to switch to their app's actual client-id value once this workflow's own input changes.