fix: undefined ignoreScripts config option

[jessedobbelaere]

In #4567 I had an issue in my repository. We were using trustLevel: high but we did not want to execute post-scripts after bumping composer dependencies. The ignoreScripts: true option was added in #4963 🙌 Unfortunately I could not get it to work. Initially, I thought my config was wrong and I created a config-help issue (renovatebot/config-help#522).

I had some time now to debug the issue. This seemed to be the issue:

• Added "ignoreScripts": true, to my renovate.json file
• Started a Docker container locally, but adding some debug statements in dist/manager/composer/artifacts.js to print out the value of config.ignoreScripts
• Ran renovate on a private repo. Result was that config did not even have the property ignoreScripts at all 🤔 it printed undefined as the value for ignoreScripts in the config 👎 .

If I remove the stage: 'package' from ignoreScripts – just like other options such as ignoreNpmrcFile – it works and config.ignoreScripts returns true and composer succesfully adds the --no-scripts argument 🎉

[jessedobbelaere]

One unit test failing but it's ok, looks like the snapshot needs to be updated because the ignoreScripts option appeared in the config now. Not sure yet how to update the snapshot 👀

[viceice]

Look at the jest summary after all tests done. There is a suggestion how to update snapshots. 🙃

[renovate-release]

🎉 This PR is included in version 19.185.2 🎉

The release is available on:

• GitHub release
• 19.185.2

Your semantic-release bot 📦🚀