chore: add Dependabot configuration - #210
Merged
Merged
Conversation
|
Reviews (1): Last reviewed commit: "chore: add Dependabot configuration" | Re-trigger Greptile |
Contributor
posthog-php Compliance ReportDate: 2026-08-07 10:13:01 UTC ✅ All Tests Passed!46/46 tests passed Capture Tests✅ 29/29 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
dustinbyrne
approved these changes
Aug 7, 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.
💡 Motivation and Context
Add root-level Dependabot coverage for the dependency managers used by this repository: Composer for SDK dependencies, npm for the release-metadata
package.jsonand its pnpm package-manager pin, and GitHub Actions.All three ecosystems run weekly with a seven-day default cooldown. The configuration does not set explicit reviewers; the repository-wide CODEOWNERS rule assigns
PostHog/team-client-librariesto dependency update changes.💚 How did you test it?
.github/dependabot.ymlwith Ruby's YAML parser and asserted the exact ecosystem order, complete key set, root directories, weekly intervals, seven-day cooldowns, and absence ofreviewers.pnpm install --frozen-lockfilesuccessfully.composer validate --no-check-publishsuccessfully (with the repository's existing warning about theversionfield).git diff --checksuccessfully.origin/main; it reported no actionable findings.📝 Checklist
If releasing new changes
pnpm changeto generate a change intent file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Implemented with Pi's implementation agent and the
autoreviewskill. The configuration is intentionally limited to the three package ecosystems used at the repository root, with duplicated scheduling and cooldown settings and reviewer assignment left to CODEOWNERS.