Yevhen Zavhorodnii

As workaround I may change disk_size_gb to 2 for M2 and 5 for M5 but I think it shouldn't even allow me to set disk_size_gb for M2 and M5 cluster...

Yes, and related issue was closed due to inactivity :(

@joreiche this PR https://github.com/joreiche/threagile/pull/4 is for merging this PR into your fork which later may be used in https://github.com/Threagile/threagile/pull/57

Could you please add more details on exact example when it's not working for you? Also @joreiche may share more details on using confi file instead of arguments in command...

Interestingly I'm getting this error message only if I run ```yarn upgrade``` for some exact packages (@types, @storybook/* or material)

Adding resolutions into package.json (following advice from https://stackoverflow.com/questions/71831601/ts2786-component-cannot-be-used-as-a-jsx-component) helped me to solve the issue ``` "resolutions": { "@types/react": "17.0.14", "@types/react-dom": "17.0.14" }, ```

I'm wondering why in their [example](https://github.com/apple/pkl-go-examples) they are using Go < 18, when this project is on Go 21.

Yes, as @Lupus mentioned there is an approach to have some "script" language. And even more there is a huge bunch of code written by @joreiche to improve those scripting...

Conflicts are resolved manually and changes are in master

Speaking of abandoning the project it's kind of duplicate of - https://github.com/thomvaill/log4brains/issues/113 - https://github.com/thomvaill/log4brains/discussions/108 node21 can be workarounded with adding a flag to your environment variable (NODE_OPTIONS=--openssl-legacy-provider) https://github.com/thomvaill/log4brains/pull/114