chore: bump versions

[romanz]

tools/bump-version.py core 2.11.1
tools/bump-version.py core/embed/projects/bootloader 2.1.17
tools/bump-version.py core/embed/projects/prodtest 0.3.7
tools/bump-version.py core/embed/projects/secmon 1.0.8
tools/bump-version.py legacy/firmware 1.14.2

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d4b0ca0 and 0244f2c.

📒 Files selected for processing (9)

• core/embed/projects/firmware/version.h
• core/translations/cs.json
• core/translations/de.json
• core/translations/en.json
• core/translations/es.json
• core/translations/fr.json
• core/translations/pt.json
• core/translations/signatures.json
• legacy/firmware/version.h

---

Walkthrough

This pull request updates version numbers across the firmware and translation files. The firmware patch version is incremented in both the core and legacy embedded projects. All translation JSON files (Czech, German, English, Spanish, French, Portuguese) have their header versions bumped from 2.11.0 to 2.11.1. The translations signatures snapshot is updated with new merkle root, datetime, and commit values to reflect the current state.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description lacks required sections from the template (PR setup, development status, post-merge status) and provides only bare version bump commands without context or explanation.	Add required template sections including PR setup details, development status, and post-merge status with QA notes if applicable.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: bump versions' clearly and concisely summarizes the main change: updating version numbers across multiple components.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch romanz/bump-versions

---

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: 22631390501

[romanz]

Some of the updates were done in 0a33b93.