chore(ci): Update trezor user env image to latest

[HajekOndrej]

Description

Related Issue

Resolve

Screenshots:

[coderabbitai]

Walkthrough

The changes update multiple Docker Compose configuration files to use a new version of the Docker image for the trezor-user-env-unix service. In every instance, the previous image tag b23cde1860e03c8bdaebbbc8fcbcd2cc9d6375d3 has been replaced with the new tag 6339d48f1df4f007fe5caee659e4bca3997d480a. This update is consistent across all the modified files, including configurations for different testing and CI environments. Additionally, one of the files (docker-compose.suite-dev.yml) indicates that the extends keyword is used despite it being unsupported in schema version '3'. No further changes to service settings, environment variables, volumes, or network configurations have been made.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 87d79e8 and 4299334.

📒 Files selected for processing (1)

• packages/trezor-user-env-link/src/api.ts (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (11)

• GitHub Check: build-deploy
• GitHub Check: run-desktop-tests (@group=wallet, trezor-user-env-unix bitcoin-regtest)
• GitHub Check: run-desktop-tests (@group=other, trezor-user-env-unix)
• GitHub Check: run-desktop-tests (@group=settings, trezor-user-env-unix bitcoin-regtest)
• GitHub Check: build-web
• GitHub Check: run-desktop-tests (@group=device-management, trezor-user-env-unix)
• GitHub Check: build-web
• GitHub Check: transport-e2e-test
• GitHub Check: Setup and Cache Dependencies
• GitHub Check: Analyze with CodeQL (javascript)
• GitHub Check: run-desktop-tests (@group=suite, trezor-user-env-unix)

🔇 Additional comments (2)

packages/trezor-user-env-link/src/api.ts (2)

3-3: LGTM! Good choice using the standard semver function.

The change from semverRSort to rcompare aligns better with semver's standard practices while maintaining the same functionality.

---

195-214:

✅ Verification successful

Improved method signature and implementation.

The changes make the code more robust and maintainable:

• Explicit default value in the method signature
• Better error handling through optional chaining
• More concise implementation

Verify firmware version selection logic.

Please ensure that:

1. The fallback version '2-main' is still valid
2. The version sorting works as expected with your firmware versioning scheme

Run this script to verify the firmware version selection:

---

🏁 Script executed:

#!/bin/bash
# Description: Verify firmware version selection logic
# Test 1: Check if '2-main' is still a valid version
rg -A 5 "2-main" --type ts

# Test 2: Check firmware version patterns to ensure they're compatible with semver
ast-grep --pattern 'version: $_'

Length of output: 2020

---

Firmware Version Selection Logic Verified and Method Improvements Approved

The revised implementation clearly improves the method with the following changes:

• Enhanced Method Signature: Explicitly specifies a default empty object (arg: StartEmu = {}) and uses destructuring with a default for the model.
• Robust Firmware Selection: Implements optional chaining, semver validation, and uses rcompare to select the latest version, with the fallback to '2-main' confirmed as valid.
• Conciseness & Clarity: The improved code structure not only simplifies reading but also enhances error protection.

The verification script output indicates that the fallback version '2-main' is in active use, and the version selection supports the firmware versioning scheme as intended.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.