fix: revert runOnce breaking changes #760
Merged
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.
Description, Motivation & Context
This PR restores the original
runOnce
property, which was changed in #740 without considering it a breaking change since it was an undocumented internal property. That was a mistake because consumers relied on it.The property was added back as a read-only getter in #751, which was another naive decision from me, because not only did consumers rely on reading it, but it seems (based on the Renovate passing tests percentage below) that they actually also mutate the property to change their jobs' behavior.
Related Issues
How Has This Been Tested?
Test case already present from #740.
Types of changes
Checklist:
!
after the type/scope in the title (see the Conventional Commits standard).