Skip to content

fix: Prevent forbidden token in web editor after screen restoration #2293

fix: Prevent forbidden token in web editor after screen restoration

fix: Prevent forbidden token in web editor after screen restoration #2293

Triggered via pull request March 16, 2026 15:03
@FabianDevelFabianDevel
synchronize #1968
Status Success
Total duration 11s
Artifacts

semantic-commit.yml

on: pull_request_target
Check Commit Message
5s
Check Commit Message
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Check Commit Message
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gsactions/commit-message-checker@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/