What the agent does
The agent reads what the site depends on and what already updates it, because a VitePress site usually has a handful of devDependencies and no CI to catch a bad bump. In a site laid out like vuejs/blog, package.json has eight devDependencies and no dependencies: vitepress ^1.3.4, vue ^3.5.0-beta.3, tailwindcss ^3.4.10 with @tailwindcss/typography ^0.5.14, feed ^4.2.2, gray-matter ^4.0.3, @types/node ^20.11.27 and @types/markdown-it ^12.2.3; packageManager is pnpm@9.8.0 and pnpm-lock.yaml is at lockfile version 9. There is no .github directory at all, so no Dependabot, no Renovate and no workflow; vercel.json sets cleanUrls and a cache header for /assets/, which is where the build is deployed from. The build script is vitepress build, and .vitepress/config.ts registers genFeed as buildEnd, so a build also writes feed.rss into outDir through the feed package.
Then it reads what each package is used for, since the groups should follow the blast radius and not the alphabet. .vitepress/theme/index.ts ships a custom theme with only a Layout, so the site does not use VitePress's default theme and a VitePress minor that changes default-theme components cannot break it, while one that changes createContentLoader, used in posts.data.ts and genFeed.ts, can. postcss.config.js calls tailwind() as a function with a content glob and the typography plugin, which is the Tailwind 3 API; Tailwind 4 moved configuration into CSS and dropped that call, so a major there is a migration, not an update. vue is pinned to a beta range, and the lockfile resolved 3.5.0-beta.3, so the first update will propose the current stable 3.5 line. The two @types packages only affect tsconfig.json's type check of .vitepress/**, which no script runs.
It writes .github/dependabot.yml with one npm entry at / (pnpm's lockfile is read there) on a weekly schedule with a cooldown of a few days, a site-build group for vitepress and vue so the renderer and the framework move together, a styles group for tailwindcss and @tailwindcss/typography, a types group for the two @types packages, an ignore of version-update:semver-major for tailwindcss with a comment pointing at postcss.config.js, and open-pull-requests-limit set so a quiet week is one or two pull requests. feed and gray-matter stay ungrouped, since each is one file's dependency and a failure there is easy to place. There is no github-actions entry, because there are no workflows, and the file says so in a comment rather than leaving a reader to wonder.
In its sandbox the agent validates the YAML against Dependabot's configuration schema, runs pnpm install --frozen-lockfile with the pinned pnpm, runs pnpm outdated so the pull request can list what the first site-build, styles and types pull requests would carry and which majors sit behind the ignore, and runs pnpm build once, checking that feed.rss is written with every post in posts/, so the description can say the site built cleanly on the current lockfile before Dependabot begins changing it.
Start it with one API call
POST https://api.phoenix.so/o/{org}/sessions with this body:
{
"agent": "claude",
"input": "Add Dependabot to this VitePress site. Read package.json, pnpm-lock.yaml's header, .vitepress/config.ts, .vitepress/genFeed.ts, .vitepress/theme/index.ts, .vitepress/theme/posts.data.ts, postcss.config.js, tsconfig.json and vercel.json first. Write .github/dependabot.yml with a single npm entry at the root on a weekly schedule with a cooldown of a few days, a group that keeps vitepress and vue together, a group for tailwindcss and @tailwindcss/typography, a group for the @types packages, an ignore for tailwindcss majors with a comment explaining why postcss.config.js cannot take Tailwind 4 as an update, and a low open pull request limit; add a comment saying why there is no github-actions entry. Validate the file against Dependabot's configuration schema, run pnpm install --frozen-lockfile, pnpm outdated and pnpm build, check that feed.rss is in the build output, and open a pull request that lists what the first grouped updates would include. Do not change package.json, the lockfile or any file under .vitepress.",
"resources": [
{
"url": "https://github.com/your-org/your-app"
}
]
}- Get an API key. In the console, open Settings, then API keys, and create a key for your org. Send it in the Authorization header as a Bearer token.
- Send the request. POST the body in request.json to https://api.phoenix.so/o/{org}/sessions, with your repository as the resources URL. The run starts in its own cloud sandbox.
- Read what came back. Follow the run on its live stream or wait for the run.completed webhook, then read the result and its trajectory.
What comes back
The pull request adds .github/dependabot.yml and nothing else. Its description pastes the schema validation result, the pnpm outdated table, the packages each of the three groups would carry in their first pull request, the Tailwind major held back, and the pnpm build output with the line confirming feed.rss was written.
Before merging, a reviewer decides whether vue should leave the beta range by hand first so Dependabot's first proposal is a clean minor, whether the weekly day suits the posting rhythm, and whether to add the one workflow the site lacks, a vitepress build on every pull request, so grouped updates are checked before Vercel builds them.
Run it on every Monday morning
Once Dependabot opens its grouped pull requests each week, the question is who checks that the site still builds, since the repository has no CI. An automation on the Project with a schedule trigger (cron 0 9 * * 1 in your timezone) and the prompt "for each open pull request by dependabot, install with the pinned pnpm, run pnpm build on its branch, confirm feed.rss lists every post, and comment on it with the result" runs once a week after Dependabot's slot; a pull request a bot opened fires no github trigger, so the schedule is what reaches them.
A team that keeps several VitePress sites sends this body once per repository from its own server, each a POST /o/{org}/sessions with that repository in resources and a request_id that is a UUID v5 of the repository's full name, so a retried call returns the run already started. Each run reads its own package.json: a site on the default theme gets vitepress alone in its group, and one with workflows gets a github-actions entry as well.
The use case this job follows, with its automation and trigger: Upgrade dependencies weekly.
Why run it on Rush?
A generic Dependabot file for a site this small opens eight pull requests the first Monday, one of them a Tailwind 4 bump that postcss.config.js cannot survive, with no workflow to say so. The agent reads which file uses which package and writes the groups and the ignore from that, so the first week is two or three pull requests whose scope a reviewer can see.
The schema check, the outdated table and the clean build stay with the run and are in the pull request, so the reviewer knows what is coming before it arrives. The same request runs across every documentation site a team maintains at once.
Frequently asked questions
Why is there no github-actions entry?
Because the repository has no .github/workflows directory; the site is built and deployed by Vercel from vercel.json. Dependabot refuses an entry for an ecosystem with no manifest, so the file carries a comment instead, and the first workflow added later is the moment to add that entry.
What happens with the vue beta range?
The lockfile resolved vue to 3.5.0-beta.3, and stable 3.5 releases are newer than that, so Dependabot's first site-build pull request proposes the current stable 3.5 version alongside any VitePress update. The reviewer can also move the range off the beta by hand first, which the pull request suggests.
Why hold back only the Tailwind major?
Tailwind 4 removed the tailwind() plugin call with a content option that postcss.config.js uses and moved configuration into CSS, so the bump is a migration of the theme's styles. The other packages are either minor-only in the range or used by one file (feed in genFeed.ts, gray-matter in the content loader), where a breaking change is easy to find.
Does Dependabot handle a pnpm lockfile?
Yes. The npm ecosystem covers pnpm-lock.yaml, and packageManager in package.json tells it which pnpm to resolve with. The lockfile version 9 header is what pnpm 9.8 writes, so Dependabot's updates keep the same format.
More VitePress jobs
The same job on other stacks
- Add Dependabot to a VS Code Extension (VS Code extension)
- Add Dependabot to a Chrome Extension Repository (Chrome extension)
- Add Dependabot to a CMake C++ Project (CMake)