Issue with yarn install when packages are linked to git submodules #31457
Replies: 2 comments
-
Sounds like you need cloneSubmodules, which is one of the first hits when you search Renovate docs for "submodules": |
Beta Was this translation helpful? Give feedback.
0 replies
-
Sorry for creating stupid issue, indeed there is this option that probably solves my issue. I've focused on using git-submodules and didn't think about investigating into documentation more. I'm testing it right now.
But I'm not sure if it's still renovate issue or repository configuration. Anyway will create seperate discussion if that's renovate issue. Thanks for quick answer. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
Other
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
38.66.0
Please tell us more about your question or problem
In my company we've stumbled upon special case in which renovate is not working correctly.
Some frontend teams are linking through path aliasing packages to git submodules directories.
In submodules there are git submodules.
Sadly that creates error because renovate does not recognize this and don't install these modules before executing yarn install command. Because of that in all of these projects we are receiving error message:
Tried to use git-submodules manager in renovate but sadly it only creates PRs with bump of submodules and don't resolve the issue. Best solution would be to have this preUpgradeTask but I see that's still in planning phase #8804.
Is there some other workaround available to handle this issue?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions