Our project builds have started failing on qlty web portal

[nikhilgoyal22]

Question

We are getting errors on our build

(node:20) ExperimentalWarning: Use `importAttributes` instead of `importAssertions`
(Use `node --trace-warnings ...` to show where the warning was created)
Running install...
sh -c curl https://qlty.sh/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
[REDACTED]    0     0   409k      0 --:--:-- --:--:-- --:--:--  415k

#########################################################                 80.5%
######################################################################## 100.0%
mv: cannot stat '/home/runner/.qlty/downloads/qlty-x86_64-unknown-linux-gnu/qlty': No such file or directory
error: Failed to move extracted qlty to destination
FATAL [457dca799f134065ae7058b5c757616b]: Command failed with status 1: sh -c curl https://qlty.sh/install.sh | bash
    at getFinalError (file:///home/runner/builder/node_modules/execa/lib/return/final-error.js:6:9)
    at makeError (file:///home/runner/builder/node_modules/execa/lib/return/result.js:108:16)
    at getAsyncResult (file:///home/runner/builder/node_modules/execa/lib/methods/main-async.js:167:4)
    at handlePromise (file:///home/runner/builder/node_modules/execa/lib/methods/main-async.js:150:17)
    at async runCommand (/home/runner/builder/src/utils/cmd.ts:44:12)
    at async <anonymous> (/home/runner/builder/src/commands/install.ts:8:5)
    at async install (/home/runner/builder/src/commands/install.ts:7:10)
    at async workflow (/home/runner/builder/src/utils/workflow.ts:28:5)
    at async builderRun (/home/runner/builder/src/commands/run.ts:29:3)
    at async <anonymous> (/home/runner/builder/src/commands/run.ts:22:17)

How to reproduce (optional)

Expected behavior (optional)

No response

CLI Version

We are using web

Information about Qlty configuration and environment (optional)

// Add your qlty.toml

• OS:

[brynary]

Hi @nikhilgoyal22 -- Thanks for this report, and sorry for the trouble here. This issue was caused by a bad release of the Qlty CLI which was deployed last night.

We have yanked the bad release, and it should be back to normal. Please let us know if you are having any further issues.

-Bryan