Skip to content

fix: handle invalid UUID in remove_self to prevent 500 and return 400 #1895

fix: handle invalid UUID in remove_self to prevent 500 and return 400

fix: handle invalid UUID in remove_self to prevent 500 and return 400 #1895

Triggered via pull request March 24, 2026 18:24
Status Success
Total duration 2m 18s
Artifacts

pre-commit.yml

on: pull_request
Path match check
8s
Path match check
All file linting
2m 1s
All file linting
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Path match check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: fkirc/skip-duplicate-actions@master. 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/
All file linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, pre-commit-ci/lite-action@v1.1.0. 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/