Skip to content

Group patch and minor Dependabot updates for easier approval/merging - #352

Merged
szegedi merged 1 commit into
mainfrom
szegedi/group-dependabot
Jun 16, 2026
Merged

Group patch and minor Dependabot updates for easier approval/merging#352
szegedi merged 1 commit into
mainfrom
szegedi/group-dependabot

Conversation

@szegedi

@szegedi szegedi commented Jun 15, 2026

Copy link
Copy Markdown

What does this PR do?:
Modifies Dependabot config to allo grouping patch and minor bumps into single PRs (major updates remain individual for closer review.)

Motivation:
Save time by not having to deal with individual patch update PRs.

@datadog-prod-us1-6

datadog-prod-us1-6 Bot commented Jun 15, 2026

Copy link
Copy Markdown

Pipelines

Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

Pull Request Labels | label   View in Datadog   GitHub Actions

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 84423d2 | Docs | Datadog PR Page | Give us feedback!

@github-actions

Copy link
Copy Markdown

Overall package size

Self size: 2.2 MB
Deduped: 2.56 MB
No deduping: 2.56 MB

Dependency sizes | name | version | self size | total size | |------|---------|-----------|------------| | source-map | 0.7.6 | 185.63 kB | 185.63 kB | | pprof-format | 2.2.1 | 163.06 kB | 163.06 kB | | node-gyp-build | 4.8.4 | 13.86 kB | 13.86 kB |

🤖 This report was automatically generated by heaviest-objects-in-the-universe

@szegedi szegedi added the semver-patch Bug or security fixes, mainly label Jun 16, 2026
@szegedi
szegedi enabled auto-merge (squash) June 16, 2026 09:38
@szegedi
szegedi merged commit 0089e1e into main Jun 16, 2026
127 of 130 checks passed
@szegedi
szegedi deleted the szegedi/group-dependabot branch June 16, 2026 09:42
@szegedi szegedi mentioned this pull request Aug 11, 2026
szegedi added a commit that referenced this pull request Aug 11, 2026
szegedi added a commit that referenced this pull request Aug 11, 2026
branch-diff matches commits rather than content, so it reports commits whose
changes are already on v5.x. Two thirds of its output for v5.18.0 was noise.
The skill previously said only "skip commits that would result in empty
cherry-picks", which gives no way to tell those apart from real ones.

Document the three classes actually observed:

  a. Commits subsumed by the squash-merged 5.14.2/5.14.3/5.14.4 releases.
     Enumerated per release; a closed set that will not grow.
  b. Dependabot bumps superseded by a later bump of the same package on v5.x.
     Cherry-picking one downgrades the branch.
  c. #154, the 6.0.0-pre bump on main, which must never reach a 5.x branch.

Applying these to `branch-diff v5.x main` yields exactly the 13 commits in the
v5.18.0 proposal.

Also add a `git diff --stat main` check before the version bump. An age-based
cutoff had dismissed #352 as a false positive when it was real and unapplied;
the content diff is what exposed it, so the skill now states that age alone is
not evidence and cites #352 as the counterexample.

Smaller fixes for things that misled during v5.18.0: pull both branches before
comparing, parse PR numbers from the trailing URL rather than the "(#NNN)" form
(which false-matches PR references in commit titles), clear the previous
release's worktree, and keep the version commit last on the branch.
szegedi added a commit that referenced this pull request Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver-patch Bug or security fixes, mainly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants