Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(manager/git-submodules): get recorded submodule commit #30976

Merged
merged 1 commit into from
Aug 23, 2024

Conversation

amezin
Copy link
Contributor

@amezin amezin commented Aug 23, 2024

Changes

Get submodule state recorded in git commit, not the state of the current working copy.

Context

https://github.com/amezin/renovate-submodule-fail

When persistRepoData is enabled, Renovate updates the submodule(s), and leaves the repository in that state. Next time currentDigest for the submodule(s) is detected incorrectly (because they are already updated in the working copy), so no update is detected, and pull requests are closed.

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@rarkins rarkins added this pull request to the merge queue Aug 23, 2024
Merged via the queue into renovatebot:main with commit 745978f Aug 23, 2024
38 checks passed
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 38.51.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

oxdev03 pushed a commit to oxdev03/renovate that referenced this pull request Aug 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants