Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
After a node version bump in the CLI's Dockerfile to v12.22.11, codefresh log following broke for pipelines run via the codefresh-pipeline-runner GitHub Action with: Your node version (v12.22.11) is not compatible with supported node version (<=10.x >=8.x) for this command. The CLI's log helper hard-checked the node version range and the new bundled version fell outside it.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
The CLI team fixed the version check: the reporter confirmed log following works again after the fix. Update the codefresh CLI to the latest release if you hit the node-version compatibility error when tailing pipeline-runner logs.
Source: https://github.com/codefresh-io/cli/issues/735
Source: https://github.com/codefresh-io/cli/issues/735
Shows how to fix codefresh CLI: log following breaks after node version bump. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix pulumi hangs on GitHub Actions after a Node.js version bump. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes a helpdesk agent that cannot parse GlobalProtect logs after a client update changed the format: version-tagged parsers and graceful fallback.