From b0d39e8ffb5c7c7018cdd9c36bb83e30a3ff465b Mon Sep 17 00:00:00 2001 From: Michael Uloth Date: Thu, 5 Nov 2026 07:00:45 -0500 Subject: [PATCH 1/8] ci: group security updates and let majors through ooloth/dotfiles#251 Every update was in one group per ecosystem, but a group without applies-to covers version updates only, so each security update opened a PR of its own: 18 were open at once. npm majors were ignored, so they were never proposed at all, and the limit of one open PR per ecosystem left no room for anything beside the group. Each ecosystem now has a version-update group for minor and patch releases and a security-update group for everything Dependabot flags. Majors open as their own PRs, so one breaking upgrade cannot block the rest, and the limit of 5 leaves room for them beside the groups. The monthly schedule and the 7-day cooldown are unchanged. --- .github/dependabot.yml | 36 +++++++++++++++++++++--------------- 1 file changed, 21 insertions(+), 15 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 0d74fc6..ba0023a 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -1,7 +1,10 @@ -# Keeps the npm packages and the SHA-pinned actions in .github/workflows -# current. Each ecosystem gets at most one PR a month, with every update grouped -# into it. A release is only proposed once it is 7 days old, so a compromised -# one has time to be found and pulled. +# Keeps the npm packages and the SHA-pinned actions in .github/workflows current. +# +# Version updates arrive at most monthly, and only for releases at least 7 days old, so a +# compromised release has time to be found and pulled. Minor and patch updates are grouped into +# one PR per ecosystem. Majors open as their own PRs, so one breaking upgrade cannot block the +# rest, and the PR limit leaves room for them beside the group. Security updates ignore the +# version-update groups and would open one PR per package, so they get their own group. version: 2 updates: - package-ecosystem: github-actions @@ -10,24 +13,27 @@ updates: interval: monthly cooldown: default-days: 7 - open-pull-requests-limit: 1 + open-pull-requests-limit: 5 groups: actions: - patterns: - - '*' + applies-to: version-updates + patterns: ['*'] + update-types: [minor, patch] + actions-security: + applies-to: security-updates + patterns: ['*'] - package-ecosystem: npm directory: / schedule: interval: monthly cooldown: default-days: 7 - open-pull-requests-limit: 1 + open-pull-requests-limit: 5 groups: npm: - patterns: - - '*' - # A major version can break the checks and block the whole grouped PR, so - # majors are upgraded deliberately instead. - ignore: - - dependency-name: '*' - update-types: ['version-update:semver-major'] + applies-to: version-updates + patterns: ['*'] + update-types: [minor, patch] + npm-security: + applies-to: security-updates + patterns: ['*'] From 72483365c9aac5c207c20de06e254ee8853f1941 Mon Sep 17 00:00:00 2001 From: Michael Uloth Date: Thu, 5 Nov 2026 07:03:29 -0500 Subject: [PATCH 2/8] ci: say that Dependabot PRs are never built ooloth/dotfiles#251 The slow-checks comment in ci.yml and the README said build, metadata and Lighthouse run on every ready PR, but the build job skips PRs Dependabot opens, because they get no secrets. The build job's comment named only bumped actions as first running on main. Now that npm majors open as Dependabot PRs, a bumped npm package is the larger case, so all three now say a Dependabot PR is first built after it merges. --- .github/workflows/ci.yml | 5 +++-- README.md | 2 +- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 2a5ad2c..4c5e4b7 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -64,7 +64,7 @@ jobs: - run: npm ci - run: npm run test:ci - # Slow checks - only run on main or when PR is not draft + # Slow checks - run on main and on PRs that are not drafts, except Dependabot's (see build) build: name: Build runs-on: ubuntu-latest @@ -72,7 +72,8 @@ jobs: needs: [format, lint, typecheck, test] # Dependabot PRs get no Actions secrets, so the build can't fetch content. # Skipping it also skips metadata and lighthouse, which need its output. - # Bumped actions those jobs use first run on main, after the PR is merged. + # A bumped npm package, or an action only these jobs use, is first built + # on main, after the PR is merged. if: | github.ref == 'refs/heads/main' || (github.event_name == 'pull_request' && diff --git a/README.md b/README.md index 4e3b649..903c20a 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ My personal site where I write about what I'm learning and building ๐Ÿ“. It's a - **โœจ Result types for errors** - Rust-style `Result` instead of exceptions. Errors are values that flow through function signatures, making error handling explicit - **๐Ÿงช Testable by design** - Dependency injection separates I/O from business logic, so tests can validate transformations without mocking modules - **โœ… Post-build validation** - Scripts parse the actual build output to validate OpenGraph tags, image dimensions, alt text, and SEO metadata. Builds fail if Cloudinary images are missing alt text. -- **โšก Smart CI pipeline** - Fast checks (format/lint/typecheck/test) run on every commit. Slow checks (build/Lighthouse/metadata) only run when PRs are ready. Lighthouse tests a randomized sample of URLs from the RSS feed instead of only hardcoded paths +- **โšก Smart CI pipeline** - Fast checks (format/lint/typecheck/test) run on every commit. Slow checks (build/Lighthouse/metadata) only run when PRs are ready, and not on Dependabot's PRs, which get no secrets to fetch content with. Lighthouse tests a randomized sample of URLs from the RSS feed instead of only hardcoded paths - **๐Ÿ”„ Retry with backoff** - All external API calls are wrapped with exponential backoff retry logic to handle transient failures - **๐Ÿ’พ Development caching** - First fetch hits real APIs, then results are cached locally by namespace. Zero network calls on page refresh during development - **๐Ÿ–ผ๏ธ Responsive images** - Cloudinary integration generates srcsets with 9 sizes, automatic format/quality optimization, and enforced alt text From c1a3f34158409b2e61f5994ad0dc4b266ac74ab6 Mon Sep 17 00:00:00 2001 From: Michael Uloth Date: Thu, 5 Nov 2026 07:06:16 -0500 Subject: [PATCH 3/8] ci: keep security majors and coupled packages apart ooloth/dotfiles#251 The security groups took every update type, so a security fix that needs a major landed in one PR with every other fix and could block them all, as the 18-update security PR #188 did. They now take minor and patch only, and a security major opens on its own. next with eslint-config-next, react with react-dom and their types, and vitest with @vitest/ui only work at matching versions, so a major of one alone can fail the checks. Each set now has a group, listed before the catch-all and taking majors, so it arrives as one PR. --- .github/dependabot.yml | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index ba0023a..1378860 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -3,8 +3,10 @@ # Version updates arrive at most monthly, and only for releases at least 7 days old, so a # compromised release has time to be found and pulled. Minor and patch updates are grouped into # one PR per ecosystem. Majors open as their own PRs, so one breaking upgrade cannot block the -# rest, and the PR limit leaves room for them beside the group. Security updates ignore the -# version-update groups and would open one PR per package, so they get their own group. +# rest, and the PR limit leaves room for them beside the group. Packages that only work at matching +# versions are the exception, in groups of their own that take majors too. Security updates ignore +# the version-update groups and would open one PR per package, so they get their own group, which +# also leaves majors to their own PRs. version: 2 updates: - package-ecosystem: github-actions @@ -22,6 +24,7 @@ updates: actions-security: applies-to: security-updates patterns: ['*'] + update-types: [minor, patch] - package-ecosystem: npm directory: / schedule: @@ -30,6 +33,18 @@ updates: default-days: 7 open-pull-requests-limit: 5 groups: + # Each of these sets is pinned or released in step, so one package moving alone can fail the + # checks. They arrive as one PR each, majors included. Dependabot gives a dependency to the + # first group that matches, so these come before the catch-all. + next: + applies-to: version-updates + patterns: [next, eslint-config-next] + react: + applies-to: version-updates + patterns: [react, react-dom, '@types/react', '@types/react-dom'] + vitest: + applies-to: version-updates + patterns: [vitest, '@vitest/*'] npm: applies-to: version-updates patterns: ['*'] @@ -37,3 +52,4 @@ updates: npm-security: applies-to: security-updates patterns: ['*'] + update-types: [minor, patch] From db3d8aa05275f5b966d919507e33f4aa06782cba Mon Sep 17 00:00:00 2001 From: Michael Uloth Date: Thu, 5 Nov 2026 07:06:16 -0500 Subject: [PATCH 4/8] claude: merge a Dependabot PR only after it builds locally ooloth/dotfiles#251 CI skips the build on Dependabot PRs because they get no secrets, and with majors now arriving as Dependabot PRs, one that breaks the build would pass CI and break main and npm run deploy:ci once merged. CLAUDE.md now says to run npm run build on the PR's branch first. --- CLAUDE.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index b84f0ff..ec00f39 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -43,6 +43,12 @@ const svg = await satori( This rule ensures the codebase maintains full type safety and prevents runtime errors that `any` would hide. +## Dependency Updates + +**A Dependabot PR is merged only after `npm run build` passes on its branch locally.** CI skips +the build on Dependabot PRs because they get no secrets, so a dependency update that breaks the +build passes CI, and merging it breaks `main` and every `npm run deploy:ci` until it is fixed. + ## Publishing and Deploying Blog posts live in Notion, not in this repo. `next.config.ts` sets `output: 'export'`, so the From 3b5309583526b31198e1e9b950061fd2edf07a8b Mon Sep 17 00:00:00 2001 From: Michael Uloth Date: Thu, 5 Nov 2026 22:41:53 -0500 Subject: [PATCH 5/8] ci: check Dependabot PRs by a run started by hand ooloth/dotfiles#251 The security groups took minor and patch only, but Dependabot judges a security update's type from the package's newest release, not its fix. ws 7.5.10's fix is the 7.5.11 patch, yet 8.x exists, so it would have opened alone, as would most of today's alerts. Both security groups now take every type, at the cost that a breaking fix can hold up the rest. Tailwind's two packages and the two artifact actions now arrive in one PR each, majors included, since one moving alone can fail. @types/node stays at or below the .nvmrc major, and npm's PR limit is 10, because its five version groups would otherwise leave no slot for a major. CLAUDE.md said to run npm run build locally before merging. That ran unchecked release code beside .env.local, and skipped the Metadata and Lighthouse jobs that deploy also needs. A workflow_dispatch run now runs Build, Metadata and Lighthouse on any branch with Actions secrets, while Deploy and Notify stay on main. The rule is now to check each release, start that run, and merge once it passes at the head commit. --- .github/dependabot.yml | 37 +++++++++++++++++++++++++++---------- .github/workflows/ci.yml | 19 ++++++++++++++----- CLAUDE.md | 16 +++++++++++++--- README.md | 2 +- 4 files changed, 55 insertions(+), 19 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 1378860..8a6aff2 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -2,11 +2,16 @@ # # Version updates arrive at most monthly, and only for releases at least 7 days old, so a # compromised release has time to be found and pulled. Minor and patch updates are grouped into -# one PR per ecosystem. Majors open as their own PRs, so one breaking upgrade cannot block the -# rest, and the PR limit leaves room for them beside the group. Packages that only work at matching -# versions are the exception, in groups of their own that take majors too. Security updates ignore -# the version-update groups and would open one PR per package, so they get their own group, which -# also leaves majors to their own PRs. +# one catch-all PR per ecosystem, and majors open as their own PRs. Dependabot reads the second +# number of a 0.x version as the minor, so a breaking 0.x release (satori, sharp, @lhci/cli, +# rehype-pretty-code) still lands in the catch-all. Packages that only work at matching versions +# are the exception, in groups of their own that take majors too. Security updates ignore the +# version-update groups and would open one PR per package, so they get their own group. It takes +# every update type, because Dependabot judges the type from a package's newest release rather +# than its fix (SemverGroupingRules in dependabot-core), and a narrower group would split off patch +# fixes. The cost is that a breaking fix can hold up the others in that PR. Security updates skip +# the cooldown and the coupled groups, so a fix moves only the package it patches, and a coupled +# package left behind is bumped by hand in the same PR. version: 2 updates: - package-ecosystem: github-actions @@ -17,6 +22,12 @@ updates: default-days: 7 open-pull-requests-limit: 5 groups: + # upload-artifact and download-artifact have broken compatibility across majors before (v4 + # could not read v3's artifacts), so they arrive together, majors included. Dependabot gives a + # dependency to the first group that matches, so this comes before the catch-all. + artifacts: + applies-to: version-updates + patterns: [actions/upload-artifact, actions/download-artifact] actions: applies-to: version-updates patterns: ['*'] @@ -24,24 +35,31 @@ updates: actions-security: applies-to: security-updates patterns: ['*'] - update-types: [minor, patch] - package-ecosystem: npm directory: / schedule: interval: monthly cooldown: default-days: 7 - open-pull-requests-limit: 5 + open-pull-requests-limit: 10 + # @types/node describes the Node API, so it stays at or below the major in .nvmrc. Raise this + # with .nvmrc. + ignore: + - dependency-name: '@types/node' + versions: ['>=26'] groups: # Each of these sets is pinned or released in step, so one package moving alone can fail the - # checks. They arrive as one PR each, majors included. Dependabot gives a dependency to the - # first group that matches, so these come before the catch-all. + # checks. They arrive as one PR each, majors included, for version updates only. Dependabot + # gives a dependency to the first group that matches, so these come before the catch-all. next: applies-to: version-updates patterns: [next, eslint-config-next] react: applies-to: version-updates patterns: [react, react-dom, '@types/react', '@types/react-dom'] + tailwind: + applies-to: version-updates + patterns: [tailwindcss, '@tailwindcss/*'] vitest: applies-to: version-updates patterns: [vitest, '@vitest/*'] @@ -52,4 +70,3 @@ updates: npm-security: applies-to: security-updates patterns: ['*'] - update-types: [minor, patch] diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 4c5e4b7..883a8e4 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -1,8 +1,10 @@ name: Check on: - # Rebuilds and deploys origin/main on demand, for publishing Notion content - # that has no corresponding commit here. See `npm run deploy:ci`. + # On main, rebuilds and deploys on demand, for publishing Notion content that + # has no corresponding commit here (see `npm run deploy:ci`). On any other + # branch, runs the slow checks without deploying, which is how a Dependabot + # PR is checked before merging (see build). workflow_dispatch: push: branches: [main] @@ -64,7 +66,8 @@ jobs: - run: npm ci - run: npm run test:ci - # Slow checks - run on main and on PRs that are not drafts, except Dependabot's (see build) + # Slow checks - run on main, on runs started by hand, and on PRs that are not + # drafts, except Dependabot's (see build) build: name: Build runs-on: ubuntu-latest @@ -72,10 +75,14 @@ jobs: needs: [format, lint, typecheck, test] # Dependabot PRs get no Actions secrets, so the build can't fetch content. # Skipping it also skips metadata and lighthouse, which need its output. - # A bumped npm package, or an action only these jobs use, is first built - # on main, after the PR is merged. + # To check one before merging, start this workflow on its branch with + # `gh workflow run ci.yml --ref `. A run started by hand has the + # Actions secrets, so check the releases first, as the Dependency Updates + # section of CLAUDE.md says. Deploy, and so wrangler-action, still runs + # only on main. if: | github.ref == 'refs/heads/main' || + github.event_name == 'workflow_dispatch' || (github.event_name == 'pull_request' && github.event.pull_request.draft == false && github.event.pull_request.user.login != 'dependabot[bot]') @@ -112,6 +119,7 @@ jobs: needs: build if: | github.ref == 'refs/heads/main' || + github.event_name == 'workflow_dispatch' || (github.event_name == 'pull_request' && github.event.pull_request.draft == false) steps: - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 @@ -132,6 +140,7 @@ jobs: needs: build if: | github.ref == 'refs/heads/main' || + github.event_name == 'workflow_dispatch' || (github.event_name == 'pull_request' && github.event.pull_request.draft == false) env: LHCI_GITHUB_APP_TOKEN: ${{ secrets.LHCI_GITHUB_APP_TOKEN }} diff --git a/CLAUDE.md b/CLAUDE.md index ec00f39..062e874 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -45,9 +45,19 @@ This rule ensures the codebase maintains full type safety and prevents runtime e ## Dependency Updates -**A Dependabot PR is merged only after `npm run build` passes on its branch locally.** CI skips -the build on Dependabot PRs because they get no secrets, so a dependency update that breaks the -build passes CI, and merging it breaks `main` and every `npm run deploy:ci` until it is fixed. +**A Dependabot PR is merged only after the Check workflow, started by hand on its branch, passes +Build, Metadata and Lighthouse at the commit being merged.** CI skips those jobs on Dependabot PRs, +because GitHub gives Dependabot no Actions secrets and the build fetches content with them. An +update that breaks them would pass CI, and merging it would break `main` and every +`npm run deploy:ci` until it is fixed. Dependabot rebases its branches, so a run of an earlier +commit does not count. + +The run gives the new code the build's secrets, and security updates skip the 7-day cooldown, so +check each release the PR adopts for signs of a compromised publish before starting it: a new +publisher, new install scripts, new dependencies, provenance the previous release had and this one +lacks, or a publish only hours old. Then run `gh workflow run ci.yml --ref ` and read the +result with `gh run list --workflow ci.yml --branch `. `cloudflare/wrangler-action` runs +only in Deploy, so a bump to it first runs on `main`. ## Publishing and Deploying diff --git a/README.md b/README.md index 903c20a..eccfbf7 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ My personal site where I write about what I'm learning and building ๐Ÿ“. It's a - **โœจ Result types for errors** - Rust-style `Result` instead of exceptions. Errors are values that flow through function signatures, making error handling explicit - **๐Ÿงช Testable by design** - Dependency injection separates I/O from business logic, so tests can validate transformations without mocking modules - **โœ… Post-build validation** - Scripts parse the actual build output to validate OpenGraph tags, image dimensions, alt text, and SEO metadata. Builds fail if Cloudinary images are missing alt text. -- **โšก Smart CI pipeline** - Fast checks (format/lint/typecheck/test) run on every commit. Slow checks (build/Lighthouse/metadata) only run when PRs are ready, and not on Dependabot's PRs, which get no secrets to fetch content with. Lighthouse tests a randomized sample of URLs from the RSS feed instead of only hardcoded paths +- **โšก Smart CI pipeline** - Fast checks (format/lint/typecheck/test) run on every commit. Slow checks (build/Lighthouse/metadata) only run when PRs are ready, and on Dependabot's PRs only when started by hand, since Dependabot gets no Actions secrets. Lighthouse tests a randomized sample of URLs from the RSS feed instead of only hardcoded paths - **๐Ÿ”„ Retry with backoff** - All external API calls are wrapped with exponential backoff retry logic to handle transient failures - **๐Ÿ’พ Development caching** - First fetch hits real APIs, then results are cached locally by namespace. Zero network calls on page refresh during development - **๐Ÿ–ผ๏ธ Responsive images** - Cloudinary integration generates srcsets with 9 sizes, automatic format/quality optimization, and enforced alt text From fd0ecc704ff08c3909ea158a4048aca162b13919 Mon Sep 17 00:00:00 2001 From: Michael Uloth Date: Thu, 5 Nov 2026 22:41:53 -0500 Subject: [PATCH 6/8] deploy: find only main's dispatched run ooloth/dotfiles#251 deploy-via-ci.sh found the run it started as the newest dispatched run of ci.yml on any branch. Dependabot branches are now checked by dispatching the same workflow, so one started during the lookup would be reported as the deploy. The lookup now filters to main. --- io/cloudflare/deploy-via-ci.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/io/cloudflare/deploy-via-ci.sh b/io/cloudflare/deploy-via-ci.sh index 54f347a..b217f43 100755 --- a/io/cloudflare/deploy-via-ci.sh +++ b/io/cloudflare/deploy-via-ci.sh @@ -25,8 +25,9 @@ fail() { exit 1 } +# Runs are also dispatched on Dependabot branches to check them, so only main's count. latest_dispatch_run_id() { - gh run list --workflow="$WORKFLOW" --event=workflow_dispatch --limit=1 --json databaseId --jq '.[0].databaseId // ""' + gh run list --workflow="$WORKFLOW" --branch="$BRANCH" --event=workflow_dispatch --limit=1 --json databaseId --jq '.[0].databaseId // ""' } if ! command -v gh >/dev/null 2>&1; then From 7c0935fcc345000561e5b54cf1d12228479783c5 Mon Sep 17 00:00:00 2001 From: Michael Uloth Date: Thu, 5 Nov 2026 22:47:20 -0500 Subject: [PATCH 7/8] claude: count only a dispatched run that ran the slow checks ooloth/dotfiles#251 The rule read the result with gh run list on the branch, which also lists the pull_request runs that pass with Build skipped. It now filters to workflow_dispatch runs, shows the head SHA, and counts a run only when Build, Metadata and Lighthouse succeeded. A Dependabot branch opened before this rule carries the old ci.yml, so it is rebased first. --- CLAUDE.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 062e874..889e72b 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -56,8 +56,12 @@ The run gives the new code the build's secrets, and security updates skip the 7- check each release the PR adopts for signs of a compromised publish before starting it: a new publisher, new install scripts, new dependencies, provenance the previous release had and this one lacks, or a publish only hours old. Then run `gh workflow run ci.yml --ref ` and read the -result with `gh run list --workflow ci.yml --branch `. `cloudflare/wrangler-action` runs -only in Deploy, so a bump to it first runs on `main`. +result with +`gh run list --workflow ci.yml --branch --event workflow_dispatch --json headSha,conclusion`, +and the run counts only when Build, Metadata and Lighthouse succeeded, not skipped. A branch opened +before this rule has the old `ci.yml`, which skips those jobs even when started by hand, so comment +`@dependabot rebase` on it first. `cloudflare/wrangler-action` runs only in Deploy, so a bump to it +first runs on `main`. ## Publishing and Deploying From 034ea3996642848dfab9aecd98902705acfdb5b2 Mon Sep 17 00:00:00 2001 From: Michael Uloth Date: Thu, 5 Nov 2026 23:28:58 -0500 Subject: [PATCH 8/8] ci: drop the actions security group, which can never fire ooloth/dotfiles#251 GitHub's "Secure use" reference for Actions says Dependabot creates no alerts for actions pinned to a SHA, and every action here is pinned, so actions-security could never open a PR. It is removed, and the header says why and that fixes to actions arrive as version updates. --- .github/dependabot.yml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 8a6aff2..a8c44f3 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -6,12 +6,14 @@ # number of a 0.x version as the minor, so a breaking 0.x release (satori, sharp, @lhci/cli, # rehype-pretty-code) still lands in the catch-all. Packages that only work at matching versions # are the exception, in groups of their own that take majors too. Security updates ignore the -# version-update groups and would open one PR per package, so they get their own group. It takes +# version-update groups and would open one PR per package, so npm's get their own group. It takes # every update type, because Dependabot judges the type from a package's newest release rather # than its fix (SemverGroupingRules in dependabot-core), and a narrower group would split off patch # fixes. The cost is that a breaking fix can hold up the others in that PR. Security updates skip # the cooldown and the coupled groups, so a fix moves only the package it patches, and a coupled # package left behind is bumped by hand in the same PR. +# GitHub raises no security alerts for actions pinned to a SHA, so there is no security-update group +# for them, and fixes to actions arrive as version updates. version: 2 updates: - package-ecosystem: github-actions @@ -32,9 +34,6 @@ updates: applies-to: version-updates patterns: ['*'] update-types: [minor, patch] - actions-security: - applies-to: security-updates - patterns: ['*'] - package-ecosystem: npm directory: / schedule: