Skip to content

Renovate: base images wait for a person; Node majors need dashboard approval #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
basmith7 merged 1 commit into from
Nov 1, 2026
Merged

Renovate: base images wait for a person; Node majors need dashboard approval #10

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,11 +70,14 @@ see the diff). A Node major bump lands here first (the `FROM` lines, and `node-c
## Renovate: `default.json`

The one dependency-update policy. A repo opts in with a `renovate.json` of
`{"extends": ["github>basmith7/workflows"]}` once its default branch runs shared CI (Renovate
merges only after CI passes, and a repo with no checks has nothing to wait for). Minor and patch
`{"extends": ["github>basmith7/workflows"]}` once CI gates its pull requests (Renovate merges only
after CI passes, and a repo with no checks has nothing to wait for). Minor and patch
updates arrive as one grouped PR each Monday morning and merge themselves (`platformAutomerge` is
off because free private repos have no required checks, so GitHub's own auto-merge would not
wait for CI); majors open as PRs for a person. `basmith7/workflows@main` refs are never touched.
wait for CI); majors open as PRs for a person. Base-image (`FROM`) updates come as their own PR
and wait for a person, because PR CI never builds the image; a Node major opens only when ticked on
the Dependency Dashboard, since it moves `templates/next-prisma` and node-ci's default first.
`basmith7/workflows@main` refs are never touched.

Renovate regenerates lockfiles with npm 11 (`constraints`). Its default npm 12 refuses the registry
tarball URLs in Tailwind's lockfile entries (`EALLOWREMOTE`, npm/cli#9800), and npm 10 fails on
Expand Down
14 changes: 14 additions & 0 deletions default.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@
"platformAutomerge": false,
"automergeType": "pr",
"automergeStrategy": "merge-commit",
"semanticCommits": "disabled",
"constraints": { "npm": "^11" },
"hostRules": [
{
Expand All @@ -29,6 +30,19 @@
"matchUpdateTypes": ["major"],
"automerge": false
},
{
"description": "Base images are never built by PR CI, so their updates wait for a person.",
"matchManagers": ["dockerfile"],
"groupName": "base images",
"groupSlug": "base-images",
"automerge": false
},
{
"description": "A Node major moves templates/next-prisma and node-ci first; it opens only when ticked on the dashboard.",
"matchDepNames": ["node"],
"matchUpdateTypes": ["major"],
"dependencyDashboardApproval": true
},
{
"description": "Callers track basmith7/workflows at @main on purpose; never pin or bump it.",
"matchManagers": ["github-actions"],
Expand Down
Loading