Skip to content

feat(themes): add chocomonkey theme (@Garu006) #15222

feat(themes): add chocomonkey theme (@Garu006)

feat(themes): add chocomonkey theme (@Garu006) #15222

Triggered via pull request May 15, 2026 01:38
Status Failure
Total duration 1m 37s
Artifacts 1

monkey-ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 6 warnings
ci-assets
Process completed with exit code 1.
ci-assets
@monkeytype/frontend#check-assets: command (/home/runner/work/monkeytype/monkeytype/frontend) /home/runner/setup-pnpm/node_modules/.bin/pnpm run check-assets others exited (1)
typescript(TS2339): src/ts/elements/keymap.ts#L129
Property 'main' does not exist on type 'Theme & { name: ThemeIdentifier; }'.
typescript(TS2339): src/ts/elements/keymap.ts#L128
Property 'main' does not exist on type 'Theme & { name: ThemeIdentifier; }'.
typescript(TS2339): src/ts/elements/keymap.ts#L127
Property 'bg' does not exist on type 'Theme & { name: ThemeIdentifier; }'.
typescript(TS2339): src/ts/elements/keymap.ts#L122
Property 'sub' does not exist on type 'Theme & { name: ThemeIdentifier; }'.
typescript(TS2339): src/ts/elements/keymap.ts#L121
Property 'sub' does not exist on type 'Theme & { name: ThemeIdentifier; }'.
typescript(TS2339): src/ts/elements/keymap.ts#L120
Property 'bg' does not exist on type 'Theme & { name: ThemeIdentifier; }'.
typescript(TS2339): src/ts/elements/monkey-power.ts#L241
Property 'error' does not exist on type 'Theme & { name: ThemeIdentifier; }'.
typescript(TS2339): src/ts/elements/monkey-power.ts#L241
Property 'caret' does not exist on type 'Theme & { name: ThemeIdentifier; }'.
typescript(TS2353): src/ts/states/theme.ts#L8
Object literal may only specify known properties, and 'bg' does not exist in type 'Theme & { name: ThemeIdentifier; }'.
typescript(TS2305): src/ts/states/theme.ts#L2
Module '"../constants/themes"' has no exported member 'ColorName'.
prime-cache
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci-pkg
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci-assets
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci-fe
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci-be
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
on-failure
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
pr_num
141 Bytes
sha256:5a3d726ac238f06a9ebaebdaef5283e597dd48256f2d8ac1025da6a9a43f3fbc