Repository navigation
dependabot: ignore the @getpaseo SDK packages - #101
Merged
Merged
Conversation
The SDK is re-pinned by hand only when a plugin needs a newer API, never to track a release. react-native was already ignored; the comment now says why it stays on the app's version, and why a transitive security update can still bump it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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 this changes
Dependabot now ignores
@getpaseo/client,@getpaseo/pluginand@getpaseo/protocolin every plugin folder, for both version and security updates. The SDK is re-pinned by hand, and only when a plugin needs an API a newer release adds. It is never re-pinned just to track a Paseo release (see The SDK dependency inAGENTS.md). The config comment now also says thatreact-nativestays on the version the Paseo app runs (0.81.5).react-nativewas already inignore(since #10), so this PR adds nothing new for it.What happens to the open Dependabot PRs
skills): this one should close itself. GitHub documents thatignoreapplies to version updates and security updates, and deps: bump the all-dependencies group across 1 directory with 3 updates #99 is a version update made only of the three packages ignored here. On its next run Dependabot will find nothing left to update in the group and close the PR.sprintf-js): this PR will not close deps: bump the security group across 6 directories with 1 update #100. deps: bump the security group across 6 directories with 1 update #100 is a security update named aftersprintf-js, the vulnerable transitive package, not afterreact-native. Dependabot raised it whilereact-nativewas already ignored, so ignoring the parent does not stop a security fix that has to bump it. This PR only records that in the config comment. To make deps: bump the security group across 6 directories with 1 update #100 go away, someone has to act on thesprintf-jsalert itself: dismiss it, or addsprintf-jstoignore. Either way the decision is left open here.Neither PR is commented on, closed or merged by this change.
Plugin(s) touched
Checks
.github/dependabot.ymlvalidates against the Dependabot schema (check-jsonschema --builtin-schema vendor.dependabot)package.jsonor lockfile changed.🤖 Generated with Claude Code