Skip to content

fix(ci): use PAT_TOKEN for tag push in release workflow #351

fix(ci): use PAT_TOKEN for tag push in release workflow

fix(ci): use PAT_TOKEN for tag push in release workflow #351

Triggered via pull request May 4, 2026 14:59
Status Success
Total duration 52s
Artifacts

check.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 1 warning
check: src/features/lanes/metadata.ts#L44
Invalid type "number | """ of template literal expression
check: src/converters/groundTruth/sceneUpdateConverter.ts#L228
Prefer using an optional chain expression instead, as it's more concise and easier to read
check: src/converters/groundTruth/sceneUpdateConverter.ts#L205
Prefer using an optional chain expression instead, as it's more concise and easier to read
check: src/converters/groundTruth/sceneUpdateConverter.ts#L195
Prefer using an optional chain expression instead, as it's more concise and easier to read
check: src/converters/groundTruth/sceneUpdateConverter.ts#L178
Prefer using an optional chain expression instead, as it's more concise and easier to read
check: src/converters/groundTruth/sceneUpdateConverter.ts#L170
Prefer using an optional chain expression instead, as it's more concise and easier to read
check: src/converters/groundTruth/sceneUpdateConverter.ts#L93
Unnecessary conditional, the types have no overlap
check: src/converters/groundTruth/sceneUpdateConverter.ts#L84
Invalid operand for a '+' operation. Operands must each be a number or string. Got `string | undefined`
check: src/converters/groundTruth/sceneUpdateConverter.ts#L78
Unnecessary optional chain on a non-nullish value
check: src/converters/groundTruth/sceneUpdateConverter.ts#L78
Unnecessary conditional, expected left-hand side of `??` operator to be possibly null or undefined
check
Process completed with exit code 2.
check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/