chore(ci): update create-github-app-token to suport Node.js 24

[Thalarion]

See

here
https://github.com/trezor/trezor-firmware/actions/runs/24768702531

I tested Crowdin - pull translations (manual) action and it worked as expected.

[coderabbitai]

Walkthrough

Four GitHub Actions workflow files are updated to upgrade the actions/create-github-app-token action from version 2.2.1 to 3.1.1. Alongside the version update, the input parameter name is changed from app-id to client-id across all workflows, while the secret source remains unchanged. No other workflow logic or functionality is modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is minimal and lacks required sections from the template. Core information about PR setup, development status, and testing is missing.	Add the required sections: assign yourself, add to Firmware project with Priority/Team/Sprint, set development status to 'Needs Review', and include 'Notes for QA' section with testing instructions.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating create-github-app-token action to a newer version (v3.1.1) that supports Node.js 24, addressing deprecation warnings across four workflow files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch thalarion/fix_nodejs_20_warning_in_crowdin_pull

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

en main(all)

model	device_test	click_test	persistence_test
T2T1	test(all) main(all)	test(all) main(all)	test(all) main(all)
T3B1	test(all) main(all)	test(all) main(all)	test(all) main(all)
T3T1	test(all) main(all)	test(all) main(all)	test(all) main(all)
T3W1	test(all) main(all)	test(all) main(all)	test(all) main(all)

Latest CI run: 25075468448

[M1nd3r]

• The commit hashes are valid and expected.
• I was not able to verify, whether the secret TREZOR_BOT_APP_ID is of type client-id.

nit:
Consider being more verbose in commit messages - e.g. specifying from-to versions when updating something and using the actual name of what you are updating. (example)

[M1nd3r]

We might want to use a different secret here.

IIUC, client-id and app-id are two different things. It was already possible to use client-id instead of app-id in some contexts - so I am not sure, whether secrets.TREZOR_BOT_APP_ID is app-id or client-id.

@vdovhanych Could you please confirm what type the secrets.TREZOR_BOT_APP_ID is - and if it is an app-id, could you please store client-id in secrets.TREZOR_BOT_CLIENT_ID? Thanks!

[Thalarion]

I changed it to client-id based on this warning:

App ID still works as a fallback, but changing the secret to client ID is better.