Back to Plate

Slate Monorepo Updates Need One Custom Sync Workflow

docs/solutions/workflow-issues/2026-03-31-slate-monorepo-updates-need-one-custom-pr-workflow.md

53.0.51.1 KB
Original Source

Slate Monorepo Updates Need One Custom Sync Workflow

Problem

The repo needed automated Slate dependency bumps, but the desired shape was strict: one direct sync, all Slate packages, across every manifest that pins them.

Root Cause

The missing piece was not version detection. It was workflow shape.

GitHub-native dependency bots are fine for generic updates, but the exact ask here was tighter: bundle slate, slate-dom, slate-react, and slate-hyperscript into one monorepo sync instead of splitting by dependency or directory.

Fix

Add a dedicated scheduled GitHub Actions workflow that:

  • runs once per day
  • filters updates to the Slate package family only
  • rewrites workspace manifests with npm-check-updates
  • refreshes lockfiles with pnpm install
  • syncs one stable .changeset/slate.md
  • commits and pushes straight to main with [skip release]

Rule

If a dependency automation request is really about sync shape, solve the sync shape directly.

Do not force a general-purpose dependency bot into a workflow it does not express cleanly.