Repository navigation
ci: split action majors out of the group and hold @types/node - #48
Merged
Merged
Conversation
This was referenced Sep 8, 2026
lorem-dev
changed the title
The github-actions group matched every pattern with no update-type filter, unlike the cargo and npm groups below it. Its first run put six updates in one pull request, three of them majors: tauri-action v0.6.2 to v1.0.0, setup-uv v7.6.0 to v10.0.1, and the checkout / setup-node / artifact v5-to-v7 line. That is the wrong shape for this repository specifically. tauri-action appears only in release.yml and setup-uv only in docs.yml, and neither workflow runs on a pull request -- release.yml is tag-only and docs.yml triggers on a push to main. A green pull request check therefore said nothing at all about the two riskiest lines in the diff, and the first real exercise of a v0-to-v1 bundler major would have been a release tag, across six matrix legs holding the signing secrets. Restricting the group to minor and patch makes every major arrive on its own, where the diff is small enough that its changelog is obviously the thing under review.
Dependabot offered @types/node 24.13.3 -> 26.4.1 while `engines` asks for Node >= 24 and every workflow pins `node-version: '24'`. That bump is not a dependency update so much as a claim about the runtime: tsc would start accepting APIs Node 24 does not have, the type check would stay green, and the failure would move to run time -- the one place these types exist to keep it out of. Ignoring only the major keeps the 24.x patches flowing. When the runtime moves, the types move with it in the same change.
lorem-dev
force-pushed
the
fix/dependabot-group-majors
branch
from
September 8, 2026 21:16
1517469 to
16cab69
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
github-actionsgroup matchedpatterns: ['*']with noupdate-typesfilter, unlike thecargoandnpmgroups. Its first run (#44) batched six updates into one pull request, three of them majors:tauri-apps/tauri-actionv0.6.2 -> v1.0.0astral-sh/setup-uvv7.6.0 -> v10.0.1actions/checkoutv5 -> v7,setup-nodev5 -> v7,upload-artifactv6 -> v7,download-artifactv7 -> v8tauri-actionappears only inrelease.ymlandsetup-uvonly indocs.yml. Neither workflow runs on a pull request --release.ymlis tag-only,docs.ymltriggers on a push tomain-- so #44's green checks covered none of it. The first real exercise of a v0-to-v1 bundler major would have been a release tag, across six matrix legs holding the signing secrets.Restricting the group to
minorandpatchmakes every major arrive alone.Note: Dependabot reads this file from the default branch, so the new grouping only takes effect once it reaches
main. #44 is closed in the meantime; the action bumps will come back split after the nextdevelop -> mainmerge.