Skip to content

fix: make expect(..., message) consistent as error message prefix #5640

fix: make expect(..., message) consistent as error message prefix

fix: make expect(..., message) consistent as error message prefix #5640

Triggered via pull request April 7, 2026 03:59
@hi-ogawahi-ogawa
labeled #10068
Status Failure
Total duration 6s
Artifacts

issue-labeled.yml

on: pull_request_target
reply-labeled
3s
reply-labeled
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
reply-labeled
[🚨 AC] Resource not accessible by integration
reply-labeled
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777. 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/