fix: use CLIDir for dolt remote operations instead of root Path (GH#2… #7271
ci.yml
on: push
Check version consistency
6s
Check doc flags freshness
53s
Check for .beads changes
0s
Test (Windows - smoke)
1m 28s
Check formatting
14s
Lint
1m 39s
Test Nix Flake
41s
Matrix: test
Annotations
1 error and 8 warnings
|
Test Nix Flake
Process completed with exit code 1.
|
|
Test (macos-latest)
icu4c@78 78.2 is already installed and up-to-date.
To reinstall 78.2, run:
brew reinstall icu4c@78
|
|
Test (Windows - smoke)
Back off 19.973 seconds before retry.
|
|
Test (Windows - smoke)
Failed to download action 'https://api.github.com/repos/actions/setup-go/zipball/4b73464bb391d4059bd26b0524d20df3927bd417'. Error: Response status code does not indicate success: 502 (Bad Gateway). 0C01:1F5B09:17ADBE:62E63C:69B218F3
|
|
Lint
Back off 28.9 seconds before retry.
|
|
Lint
Failed to download action 'https://api.github.com/repos/actions/setup-go/tarball/4b73464bb391d4059bd26b0524d20df3927bd417'. Error: Response status code does not indicate success: 502 (Bad Gateway). F440:28ABAB:3569AF:3656E6:69B218F4
|
|
Test (ubuntu-latest)
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. 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/
|
|
Test (ubuntu-latest)
Back off 14.206 seconds before retry.
|
|
Test (ubuntu-latest)
Failed to download action 'https://api.github.com/repos/codecov/codecov-action/tarball/671740ac38dd9b0130fbe1cec585b89eea48d3de'. Error: Response status code does not indicate success: 502 (Bad Gateway). E009:B7AEF:358748:367530:69B218F5
|