Skip to content

ci: add the weekly toolchain bump workflow - #14

Merged
pauldvlp merged 2 commits into
mainfrom
ci/toolchain-workflow
Jul 23, 2026
Merged

ci: add the weekly toolchain bump workflow#14
pauldvlp merged 2 commits into
mainfrom
ci/toolchain-workflow

Conversation

@pauldvlp

Copy link
Copy Markdown
Owner

Dependabot updates dependencies but never the packageManager pin. This repo is on pnpm 11.12.0 while 11.17.0 is current, with every dependency PR green the whole time. corepack reads packageManager, so moving the pin is the upgrade.

Runs Mondays ~06:17 UTC, plus workflow_dispatch.

What it does not touch

engines.node. Raising the published floor drops end users and is a breaking release — a decision, not something an automation makes. The CI Node stays a manual bump when a new Active LTS lands.

Why the gates run inside the job

Under GITHUB_TOKEN the PR it opens has its checks parked in action_required until approved by hand, so the PR CI cannot be the verification. The job runs ci.yml's own gates itself: lint, format:check, typecheck, build, test.

E2E is deliberately skipped — a browser install for a package-manager pin is not worth six minutes every Monday.

Swapping GH_TOKEN for a fine-grained PAT makes it fully hands-off; that trade (a standing credential vs. one click a week) is documented in the workflow header.

Guard

If last week's bump PR is still open, the run exits before doing any work rather than colliding on the branch name.

Note: schedule only fires from the default branch, so nothing runs until this merges.

Dependabot updates dependencies but never the packageManager pin — this
repo has sat on pnpm 11.12.0 while 11.17.0 shipped, with every dependency
PR green. corepack reads packageManager, so moving the pin is the upgrade.

Under GITHUB_TOKEN the resulting PR's checks stay in action_required until
approved, so the job runs ci.yml's gates itself: lint, format:check,
typecheck, build, test. E2E is skipped — a browser install for a pin bump
isn't worth it every Monday.

engines.node is deliberately untouched: raising the published floor drops
users and is a breaking release, not something an automation decides.

Guards against re-running while last week's bump PR is still open, which
would collide on the branch name.
@pauldvlp
pauldvlp force-pushed the ci/toolchain-workflow branch from e7473ec to b7393bc Compare July 23, 2026 21:20
@pauldvlp
pauldvlp merged commit e13bbe5 into main Jul 23, 2026
4 checks passed
@pauldvlp
pauldvlp deleted the ci/toolchain-workflow branch July 23, 2026 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant