Repository navigation
fix: unblock Dependabot updates with stale PR base metadata - #30
Merged
Merged
Conversation
tonyputi
approved these changes
Nov 17, 2026
This was referenced Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #29
Regression evidence
Live finding and follow-up
myki#59 and myki#60 report cached PR base.sha 4fa3df89e5c9670935ffc170b09b8b369fe2317e while actual main is ec5d46c0c5d5a4d11c087ffe6891ef16ad49581a. The previous guard therefore defers eligible PRs indefinitely. Evidence: https://github.com/tonyputi/myki/actions/runs/44091650353 .
myki#58 has a genuine conflict and must remain blocked. Earlier owner branch rewrites and native merge of myki#57 are not evidence of this updater doing branch writes.
After owner review/merge, repin the myki consumer and repeat real observation under tonyputi/myki#61. No real branch update using this fix is claimed yet. No approvals, manual merges, force pushes, credentials or protection changes were performed.