Standardize maintenance across your Docusaurus sites and reduce security PR noise

[omry]

I like Docusaurus. I like it so much that I now maintain eight sites.

Each one adds upkeep: Node versions, package-manager configuration, security alerts, and automated PRs competing for attention. Multiply that across several sites, and the maintenance adds up.

I wanted fewer maintenance and security PRs to review, with a consistent security policy across all my sites. So I built reusable GitHub Actions:

• Batched PRs, with at most one for security fixes and one for routine upgrades.
• Validation results from a frozen install and your project’s checks.
• Your cadence and cooldown, with separate schedules for security and routine upgrades.
• Optional shared defaults to apply the same toolchain, cooldown, and maintenance policy across your projects.

Here’s a security PR with grouped fixes, validation results, and advisory links:

An optional fleet monitor checks that installations still follow their configured policy. It reports setup drift in one central issue and closes it after recovery. Here’s the public Hydra and OmegaConf example:

It started with Docusaurus and now supports other standalone npm and pnpm projects too. You review and merge the proposals.

Repository and setup guide →