Use RenovateBot for API docs version in build #952
Merged
Conversation
This file contains 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
|
Unfortunately there's no good way to test this (irony!) that I can see, and so I'm going to merge it and evaluate. I did check the regex in a regex tester and it worked as expected, plus I have the prior PRs I've done elsewhere with this technique. |
github-actions bot
pushed a commit
that referenced
this pull request
Jul 28, 2024
* basic first attempt * Update the depName 756c38e
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.
This introduces a RenovateBot custom manager.
In the
build-process.ymlfile, it will look for the version inNUNIT_VERSION_FOR_API_DOCS, and will suggest an update for it when a new version of NUnit is published.This ensures that our docs get PRs to stay up to date when a new version of NUnit is released.
Supports #941. Going to choose to leave it open for now because I have to merge this first before I can see if it's successful (I should see a PR generated to update to 4.1.0.