Syntax checking for scripts

[tpowell-progress]

Description

Related Issue

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
3 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Stromweld]

Looks like it's not failing the job properly when there are findings https://github.com/chef/mixlib-install/actions/runs/21884292128/job/63175040749?pr=419#step:6:10

[tpowell-progress]

Looks like it's not failing the job properly when there are findings https://github.com/chef/mixlib-install/actions/runs/21884292128/job/63175040749?pr=419#step:6:10

🤔 looks like those are all warnings, but i'll need to think about them

[Stromweld]

for some reason the job name says warnings only. But the very first one in that job is an error.

In ./.expeditor/run_linux_tests.sh line 15:
bundle exec $@
            ^-- SC2068 (error): Double quote array expansions to avoid re-splitting elements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
3 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud