Skip to content

fix: clarify null value handling in traits merge mechanism #2169

fix: clarify null value handling in traits merge mechanism

fix: clarify null value handling in traits merge mechanism #2169

Triggered via pull request March 19, 2026 11:05
@sahaiashsahaiash
synchronize #1188
Status Success
Total duration 11s
Artifacts

automerge-for-humans-merging.yml

on: pull_request_target
automerge-for-humans
8s
automerge-for-humans
Fit to window
Zoom out
Zoom in

Annotations

1 warning
automerge-for-humans
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7, pascalgn/automerge-action@22948e0bc22f0aa673800da838595a3e7347e584. 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/