Add Dependabot for dependency updates#860
Open
timhaines wants to merge 2 commits into
Open
Conversation
Contributor
Greptile SummaryThis PR adds controlled Dependabot version updates across the repository.
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (2): Last reviewed commit: "Add npm ecosystem for the local-viewer f..." | Re-trigger Greptile |
Adds .github/dependabot.yml so uv dependencies and GitHub Actions stay current automatically, complementing the existing pre-commit.ci hook autoupdates. uv updates are ungrouped (per-package, capped at 5/week) so each can be reviewed and CI-tested on its own; Actions are grouped into one weekly PR. A short 7-day cooldown lets new releases age before a PR opens, with cryptography excluded so security fixes aren't delayed. Dependabot is also told to respect the deliberate version caps in pyproject.toml -- cryptography <49 (usestrix#859), openai <2.45 (usestrix#748), and the openai-agents ==0.14.6 migration pin -- so it doesn't open bumps past them that would only fail CI or be closed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
timhaines
force-pushed
the
add-dependabot
branch
from
July 23, 2026 04:42
10c026c to
8c8c524
Compare
timhaines
added a commit
to timhaines/strix
that referenced
this pull request
Jul 23, 2026
Every `uses:` in build-release.yml was a mutable tag; the `release` job has `contents: write` and publishes the binaries users install, so a compromised action (tj-actions / CVE-2025-30066 pattern) could tamper the release. Pin all six actions to the commit each @major resolves to today (concrete version in a trailing comment; setup-uv's annotated tag dereferenced to its commit, not the tag object, so Dependabot tracks it). Also add a top-level `permissions: contents: read` (the release job keeps its explicit write) and `persist-credentials: false` on the build checkout. actionlint passes. Pairs with usestrix#860 (Dependabot github-actions keeps the pins current). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
timhaines
added a commit
to timhaines/strix
that referenced
this pull request
Jul 23, 2026
Every `uses:` in build-release.yml was a mutable tag; the `release` job has `contents: write` and publishes the binaries users install, so a compromised action could tamper the release. Action tag-hijacking keeps recurring (aquasecurity/trivy-action, 75 tags, Mar 2026 TeamPCP; tj-actions, 2025; codfish/semantic-release-action, Jun 2026) and SHA-pinned workflows were immune each time. Pin all six actions to the commit each @major resolves to today (concrete version in a trailing comment; setup-uv's annotated tag dereferenced to its commit, not the tag object, so Dependabot tracks it). Also add a top-level `permissions: contents: read` (the release job keeps its explicit write) and `persist-credentials: false` on the build checkout. actionlint passes. Pairs with usestrix#860 (Dependabot github-actions keeps the pins current). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The React/Vite SPA under strix/viewer/frontend is a second package ecosystem (package-lock.json v3) that was going unmonitored. Add it with the same shape as the uv block — ungrouped, capped at 5 PRs/week, 7-day cooldown. No ignores: every dep is a plain caret range with no cap. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
timhaines
force-pushed
the
add-dependabot
branch
from
July 23, 2026 08:19
7237807 to
9852781
Compare
bearsyankees
pushed a commit
that referenced
this pull request
Jul 23, 2026
…862) Every `uses:` in build-release.yml was a mutable tag; the `release` job has `contents: write` and publishes the binaries users install, so a compromised action could tamper the release. Action tag-hijacking keeps recurring (aquasecurity/trivy-action, 75 tags, Mar 2026 TeamPCP; tj-actions, 2025; codfish/semantic-release-action, Jun 2026) and SHA-pinned workflows were immune each time. Pin all six actions to the commit each @major resolves to today (concrete version in a trailing comment; setup-uv's annotated tag dereferenced to its commit, not the tag object, so Dependabot tracks it). Also add a top-level `permissions: contents: read` (the release job keeps its explicit write) and `persist-credentials: false` on the build checkout. actionlint passes. Pairs with #860 (Dependabot github-actions keeps the pins current). Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Author
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.
Small quality-of-life PR. Dependabot's security updates already run here (e.g. #852, bumping setuptools) — but with no committed config there's no cooldown, no GitHub Actions coverage, and nothing guarding your deliberate version caps. This adds a
.github/dependabot.ymlfor that controlled layer, alongside the existing pre-commit.ci hook autoupdates.A few light defaults:
pull_requestworkflow in the repo today, so these arrive on review rather than a green check; ungrouped is what keeps that review tractable, and it's easy to switch togroups:later if the volume annoys you.strix/viewer/frontend) — the tree's second package ecosystem — same shape as uv.# vX.Y.Zcomment, Dependabot bumps both the SHA and the comment, so the pins stay pins and just move forward. Order doesn't matter — whichever lands second picks up the other.cryptographyis excluded too.ignorerules so Dependabot won't propose bumps past them:cryptography(<49, fix(deps): cap cryptography <49 to keep Intel macOS universal2 wheel #859),openai(<2.45, fix(deps): cap openai<2.45 and add litellm[proxy] so fresh installs can run #748), and theopenai-agents==0.14.6migration pin. In-range patch/minor updates below each cap still flow. (Theopenai-agentspin is the one most worth a second look — drop that entry if you'd rather be nudged when a new SDK release lands.)There's also a commented-out
dockerentry for the sandbox image, ready to enable once its base is pinned off:latest.The cooldown here is the updater layer. The matching resolver-layer cooldowns — so manual/local updates age too — are in #861 (uv) and #864 (npm).
To activate: merging doesn't start it on its own — enable it once under Settings → Code security → Dependabot → Dependabot version updates. Runs then show under Insights → Dependency graph → Dependabot (first PRs arrive on the weekly schedule).