Skip to content

Add T3T1 device authenticity pubkeys #18480

Add T3T1 device authenticity pubkeys

Add T3T1 device authenticity pubkeys #18480

Triggered via pull request April 12, 2024 15:28
Status Failure
Total duration 9m 25s
Artifacts

validation.yml

on: pull_request
Setup and Cache Dependencies
2m 36s
Setup and Cache Dependencies
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 8 warnings
Type Checking
Property 'T3T1' is missing in type '{ T1B1: never[]; T2T1: never[]; T2B1: never[]; }' but required in type 'Record<"T1B1" | "T2T1" | "T2B1" | "T3T1", FirmwareRelease[]>'.
Type Checking
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ connect: boolean; T1B1: string | false; T2T1: string | false; T2B1: string | false; }'.
Type Checking
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ connect: boolean; T1B1: string | false; T2T1: string | false; T2B1: string | false; }'.
Type Checking
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ T1B1: string; T2T1: string; T2B1?: undefined; } | { T1B1: string; T2T1: string; T2B1?: undefined; } | { T1B1: string; T2T1: string; T2B1: string; }'.
Type Checking
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ T1B1: { name: string; colors: {}; }; T2T1: { name: string; colors: {}; }; T2B1: { name: string; colors: { '1': string; '2': string; '3': string; '4': string; '5': string; }; }; }'.
Type Checking
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type 'FirmwareRange'.
Type Checking
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ connect: boolean; T1B1: string | false; T2T1: string | false; T2B1: string | false; }'.
Type Checking
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type 'FirmwareRange'.
Type Checking
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type 'FirmwareRange'.
Type Checking
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type 'FirmwareRange'.
Build libs for publishing
Property 'T3T1' is missing in type '{ T1B1: never[]; T2T1: never[]; T2B1: never[]; }' but required in type 'Record<"T1B1" | "T2T1" | "T2B1" | "T3T1", FirmwareRelease[]>'.
Build libs for publishing
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ connect: boolean; T1B1: string | false; T2T1: string | false; T2B1: string | false; }'.
Build libs for publishing
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ connect: boolean; T1B1: string | false; T2T1: string | false; T2B1: string | false; }'.
Build libs for publishing
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ T1B1: string; T2T1: string; T2B1?: undefined; } | { T1B1: string; T2T1: string; T2B1?: undefined; } | { T1B1: string; T2T1: string; T2B1: string; }'.
Build libs for publishing
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ T1B1: { name: string; colors: {}; }; T2T1: { name: string; colors: {}; }; T2B1: { name: string; colors: { '1': string; '2': string; '3': string; '4': string; '5': string; }; }; }'.
Build libs for publishing
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type 'FirmwareRange'.
Build libs for publishing
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type '{ connect: boolean; T1B1: string | false; T2T1: string | false; T2B1: string | false; }'.
Build libs for publishing
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type 'FirmwareRange'.
Build libs for publishing
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type 'FirmwareRange'.
Build libs for publishing
Element implicitly has an 'any' type because expression of type 'DeviceModelInternal' can't be used to index type 'FirmwareRange'.
Setup and Cache Dependencies
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Other Checks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Type Checking
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Linting and formatting
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Linting and formatting: packages/connect-explorer-theme/src/components/locale-switch.tsx#L7
There should be at least one empty line between import groups
Linting and formatting: packages/connect-explorer-theme/src/components/locale-switch.tsx#L8
`@trezor/components` import should occur before import of `../contexts`
Build libs for publishing
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit Tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/