Issue #22006 has been updated by k0kubun (Takashi Kokubun).
But this made me think that perhaps this mechanism should be a composite action or something similar? Then you don't need to update it in so many places (currently 47) when something changes.
I'm not sure what you're proposing. The main work is already delegated to ruby/ruby through workflow_dispatch, which is kind of a composite action already, and most of the changes should not happen in 47 different places. I don't know when `app-id` will be dropped but the interface of workflow communication shouldn't be that stable, so updating 47 places when that happens seems acceptable to me. ---------------------------------------- Misc #22006: Usage of deprecated input in gem sync workflows https://bugs.ruby-lang.org/issues/22006#change-117041 * Author: Earlopain (Earlopain _) * Status: Open ---------------------------------------- `create-github-app-token` deprecated `app-id` in favor of `client-id` in https://github.com/actions/create-github-app-token/releases/tag/v3.1.0. Since it will probably be removed in the next major version, all workflow files need to be updated eventually. I also noticed that `convictional/trigger-workflow-and-wait` has been archived (https://github.com/convictional/trigger-workflow-and-wait). This shouldn't matter much, it is docker-based and should continue to work for a long time unless github does some API change. But this made me think that perhaps this mechanism should be a composite action or something similar? Then you don't need to update it in so many places (currently 47) when something changes. -- https://bugs.ruby-lang.org/