Skip yarn for plugins with no dependencies#9999
Conversation
|
Seems to have worked fine: |
dbb5e4b to
d248569
Compare
| # Log yarn version being used | ||
| yarn_version = `yarn --version`.strip | ||
| puts " Yarn version: #{yarn_version}" | ||
|
|
There was a problem hiding this comment.
This part is actually not necessary, because Yarn itself will emit it's version when we run it.
|
What does this actually save us, now that I think about it. Unless we remove yarn/yarn.lock/package.json, then all this does is really trim down the amount of text, right? |
|
Yeah, it might look like that, but we don’t need to remove But like I said, if we’re planning to add test/lint packages or anything at plugin level soon, then there’s probably no point in doing this now. |
d248569 to
85cf386
Compare
|
Some comments on commit asirvadAbrahamVarghese@85cf386 lib/tasks/manageiq/ui_tasks.rake
|
|
Checked commit asirvadAbrahamVarghese@85cf386 with ruby 3.3.10, rubocop 1.86.0, haml-lint 0.73.0, and yamllint 1.37.1 |
PR to skip
yarnstep for plugins with no dependencies or devDependencies. In such cases, running Yarn doesn’t serve any purpose. As a follow-up, we can also remove yarn and engines from those plugins, reducing maintenance overhead and avoiding repeated upgrade PRs.