Skip to content

Build 334 - version-patch #231

Build 334 - version-patch

Build 334 - version-patch #231

Triggered via pull request June 9, 2026 11:29
@ziimkziimk
labeled #738
334
Status Success
Total duration 2m 23s
Artifacts

cicd_npm-publish.yml

on: pull_request
publish  /  ...  /  pre-publish
10s
publish / Package Checks / pre-publish
publish  /  ...  /  Run Unit & Functional Tests (Base Version)
53s
publish / Package Test / Run Unit & Functional Tests (Base Version)
publish  /  ...  /  Check Supported Versions
3s
publish / Package Test / Check Supported Versions
Matrix: publish / Package Test / run-other-supported-versions-tests
publish  /  ...  /  package-publish
1m 0s
publish / Package Publish / package-publish
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
publish / Package Test / Run Unit Tests (Node-20)
Both node-version and node-version-file inputs are specified, only node-version will be used
publish / Package Test / Run Unit Tests (Node-18)
Both node-version and node-version-file inputs are specified, only node-version will be used
publish / Package Publish / package-publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pipedrive/gha-command-retry@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/