Configure Dependabot for npm and GitHub Actions#222
Merged
Conversation
The repo had no dependabot.yml, so only security updates ran and they opened PRs that bump npm dev-dependencies to brand-new versions which CI's JFrog db-npm registry blocks under its 7-day package cooldown, failing every check. Disable routine npm version-update PRs (security updates only) and enable GitHub Actions updates with a 7-day cooldown, matching the other Databricks SDK repos. Co-authored-by: Isaac
Divyansh-db
approved these changes
Jun 16, 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
2 participants
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.
Summary
Adds
.github/dependabot.yml, which the repository was missing entirely. It disables routine npm version-update PRs (leaving Dependabot security updates on) and enables GitHub Actions updates on a 7-day cooldown, matching the configuration already used by the other Databricks SDK repositories (databricks-sdk-go,databricks-sdk-py,databricks-sdk-java) and theappkitnpm repository.Why
The repository has no Dependabot configuration on
main, so Dependabot runs in its default mode: security updates only, with no cooldown, grouping, or version-update control. Those security-update PRs are not mergeable here. For example, #213 (esbuild advisoriesGHSA-g7r4-m6w7-qqqr/GHSA-gv7w-rqvm-qjhr) bumps the npm dev-toolchain (vite,vitest,@vitest/*) to brand-new versions, and every CI job fails atjf npm ci. The failure is not a code break: CI installs through the JFrogdb-npmregistry, which enforces a7d-cooldowncuration policy that blocks any package version less than 7 days old ("Package version is immature 7d"). Dependabot proposed 0-day-old versions, so the install is rejected before any test runs.Leaving the repository unconfigured is not viable: simply enabling npm version updates would reproduce this failure at scale, since every routine bump would also target freshly published versions that the 7-day cooldown blocks, across 60+ workspace packages. The other Databricks SDK repos solved this by disabling package-ecosystem version updates (
open-pull-requests-limit: 0) and keeping only GitHub Actions updates with a cooldown;appkitapplies exactly this shape to an npm project. This PR brings sdk-js in line with that standard.Note on scope:
cooldownapplies only to version updates, not security updates (GitHub docs), so this config does not by itself make security-update PRs like #213 pass — those remain blocked by the registry cooldown until their target versions mature. What it does fix is the systemic problem: it prevents a flood of unmergeable routine version-update PRs and keeps CI action pins current (which also clears the current "Node.js 20 actions are deprecated" warning, sinceci.yml/docs.ymlstill pinactions/checkout@v4).What changed
Interface changes
None.
Behavioral changes
open-pull-requests-limit: 0. Dependabot security updates are unaffected and continue to open (their internal limit is fixed and not controlled by this setting).cooldown: default-days: 7, so only action releases at least 7 days old are adopted. The generated.github/workflows/tagging.ymlis excluded viaexclude-paths.Internal changes
Adds a single configuration file,
.github/dependabot.yml. No source, build, or test changes.How is this tested?
Configuration-only change. Validated by mirroring the schema of the existing, in-production sibling configs (
databricks-sdk-go,databricks-sdk-py,databricks-sdk-java,appkit), which are confirmed to be valid and to produce working Dependabot PRs. No automated tests apply.This PR adds only CI/repository configuration and has no consumer-facing effect, so no changelog entry is required.
NO_CHANGELOG=true
This pull request and its description were written by Isaac.