Skip to content

Bump picomatch in /src in the npm_and_yarn group across 1 directory #1043

Bump picomatch in /src in the npm_and_yarn group across 1 directory

Bump picomatch in /src in the npm_and_yarn group across 1 directory #1043

Triggered via push March 26, 2026 15:42
Status Success
Total duration 2m 33s
Artifacts

deploy.yml

on: push
Set Env Vars
3s
Set Env Vars
Matrix: build_and_deploy
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build and Deploy / stg
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, byu-oit/github-action-codedeploy@v2, byu-oit/github-action-end-standard-change@v2, byu-oit/github-action-start-standard-change@v2, byu-oit/github-action-tf-plan-analyzer@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/
Build and Deploy / stg
No change-sys-id was provided. Skipping end-standard-change because start-standard-change likely no-oped.
Build and Deploy / stg
Skipping Standard Change RFC creation because this appears to be a non-production deployment. Set run-in-non-production to true if you want to create RFCs in sandbox.
Build and Deploy / stg
[DivvyCloud]: Scan completed, but with warnings.