Skip to content

PrivSignal Lockfile Refresh #115

PrivSignal Lockfile Refresh

PrivSignal Lockfile Refresh #115

Triggered via workflow run March 14, 2026 03:33
@simon-botsimon-bot
completed 7f99704
Status Success
Total duration 4m 22s
Artifacts
Refresh lockfile after required checks
4m 18s
Refresh lockfile after required checks
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Refresh lockfile after required checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-elixir@v1. 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/
Refresh lockfile after required checks
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention