Repository navigation
Point Dependabot at staging - #302
Merged
Merged
Conversation
Dependabot reads its configuration from the default branch, so the target-branch has to be set here for it to apply. Releases are tagged on staging; updates merged into master never reached a release (org.json 20260814 is on master but not on staging). The file matches the one the staging sync carries, so the next release merge does not conflict.
Dependency security scanScanned 24 resolved dependencies, failing on HIGH and above. Result: passed |
Code coverage
Least covered classes (10 shown)
|
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.
What
Sets
target-branch: stagingin.github/dependabot.ymlonmaster. Dependabot reads its configuration from the default branch only, so the setting has to land here to take effect.Why
Releases are tagged on
staging. Version updates merged intomasternever reach a release: org.json20260814is onmasterbut not onstagingtoday. Security updates still open againstmaster(GitHub does not applytarget-branchto them), which the file's comment now says.The file is identical to the one #303 carries to
staging, so the next release merge does not conflict.🤖 Generated with Claude Code