consolidate-deps
Skill1.7k starsChanged 5 days agoApache-2.0View on GitHub
Use when consolidating open dependabot PRs, or bumping dependency, Maven plugin, or GitHub Actions versions in db-scheduler ("bump versions", "merge the dependabot PRs", "dependency updates", "low-hanging version upgrades").
- Commits and pushes
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about kagkarlsson/db-scheduler
- Stack Overflow“Is Spring's built in Scheduler persistent.?”Stack Overflow · Dec 19, 2015 · 13 votes
- A Hacker News story“Show HN: db-scheduler – a simple cluster-friendly task-scheduler for Java”Hacker News · Nov 21, 2018 · 7 points
- A Hacker News story“Db-scheduler, a simple cluster-friendly task scheduler gets Spring Boot support”Hacker News · Aug 8, 2019 · 2 points
- Stack Overflow“looking for persistent timers for a spring application”Stack Overflow · Dec 19, 2015 · 2 votes
- bekk/db-scheduler-ui“AutoConfiguration: Use DbSchedulerCustomizer#dataSource”GitHub · Feb 27, 2025 · 1 reactions
The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 57
Talked about on GitHub, Stack Overflow and Hacker News (57 times).
On GitHub · 50
- Feb 27, 2025AutoConfiguration: Use DbSchedulerCustomizer#dataSource — bekk/db-scheduler-ui1 reaction
- Nov 14, 2026build(deps): bump the maven-dependencies group with 4 updates — SophonHQ/Sophon0 reactions · 1 comment
- Nov 13, 2026Bump com.github.kagkarlsson:db-scheduler from 16.12.0 to 17.0.0 — DependencyTrack/dependency-track0 reactions · 1 comment
- Nov 12, 2026chore(deps): Bump the java group across 1 directory with 9 updates — fixedevelloper/csimmo0 reactions
- Nov 11, 2026Bump com.github.kagkarlsson:db-scheduler from 16.12.0 to 17.0.0 — dmaiken/konifer0 reactions · 1 comment
45 more on GitHub
- Nov 9, 2026Bump com.github.kagkarlsson:db-scheduler from 16.12.0 to 17.0.0 in /spring-boot-containers — muzir/softwareLabs0 reactions
- Nov 9, 2026Bump com.github.kagkarlsson:db-scheduler from 16.12.0 to 17.0.0 — quarkiverse/quarkus-db-scheduler0 reactions
- Nov 9, 2026Bump the maven-dependencies group with 4 updates — AxonIQ/axoniq-framework0 reactions · 1 comment
- Aug 28, 2026Dependency updates — aanbrn/axon-showcase0 reactions · 1 comment
- Aug 9, 2026chore(deps): bump com.github.kagkarlsson:db-scheduler-spring-boot-4-starter from 16.7.0 to 16.12.0 in /backend — DeepSQLAI/deepsql0 reactions
- Aug 1, 2026Bump the all-non-major-updates group across 1 directory with 11 updates — streckeisen-dev/MyCVHub0 reactions · 1 comment
- Jul 17, 2026chore(deps): Bump com.github.kagkarlsson:db-scheduler from 16.11.0 to 16.12.0 — DependencyTrack/dependency-track0 reactions · 2 comments
- Jul 1, 2026Bump the all-non-major-updates group across 1 directory with 10 updates — streckeisen-dev/MyCVHub0 reactions · 2 comments
- Jun 16, 2026Bump the minor-and-patch group across 1 directory with 14 updates — navikt/mulighetsrommet0 reactions
- Jun 15, 2026Bump the minor-and-patch group with 35 updates — navikt/mulighetsrommet0 reactions · 1 comment
- Jun 10, 2026chore(deps): Bump com.github.kagkarlsson:db-scheduler from 16.11.0 to 16.12.0 — DependencyTrack/dependency-track0 reactions · 2 comments
- Jun 9, 2026Bump the gradle-minor-patch group with 12 updates — navikt/sokos-spk-mottak0 reactions · 5 comments
- Jun 8, 2026Bump the minor-and-patch group across 1 directory with 29 updates — navikt/mulighetsrommet0 reactions · 4 comments
- Jun 8, 2026Bump the minor-and-patch group with 6 updates — navikt/mulighetsrommet0 reactions · 1 comment
- Jun 5, 2026chore(deps): Bump com.github.kagkarlsson:db-scheduler from 16.10.0 to 16.11.0 — DependencyTrack/dependency-track0 reactions · 2 comments
- Jun 4, 2026Bump com.github.kagkarlsson:db-scheduler from 16.7.1 to 16.12.0 — dmaiken/konifer0 reactions · 1 comment
- Jun 3, 2026Bump the minor-and-patch group with 48 updates — navikt/mulighetsrommet0 reactions
- Jun 3, 2026Bump the all-non-major-updates group in /backend with 9 updates — streckeisen-dev/MyCVHub0 reactions · 2 comments
- May 31, 2026chore(deps): bump the maven-dependencies group across 1 directory with 14 updates — AxonIQ/AxonFramework0 reactions · 1 comment
- May 29, 2026Bump com.github.kagkarlsson:db-scheduler from 16.11.0 to 16.12.0 in /spring-boot-containers — muzir/softwareLabs0 reactions
- May 29, 2026Bump com.github.kagkarlsson:db-scheduler from 16.7.1 to 16.12.0 — quarkiverse/quarkus-db-scheduler0 reactions
- May 27, 2026Bump com.github.kagkarlsson:db-scheduler from 16.9.0 to 16.11.0 in /spring-boot-containers — muzir/softwareLabs0 reactions
- May 26, 2026Bump com.github.kagkarlsson:db-scheduler from 16.7.1 to 16.11.0 — quarkiverse/quarkus-db-scheduler0 reactions · 1 comment
- May 24, 2026chore(deps): bump the maven-dependencies group across 1 directory with 11 updates — AxonIQ/AxonFramework0 reactions · 1 comment
- May 20, 2026Bump com.github.kagkarlsson:db-scheduler from 16.9.0 to 16.10.0 in /spring-boot-containers — muzir/softwareLabs0 reactions · 1 comment
- May 20, 2026Bump com.github.kagkarlsson:db-scheduler from 16.7.1 to 16.10.0 — quarkiverse/quarkus-db-scheduler0 reactions · 1 comment
- May 20, 2026Bump com.github.kagkarlsson:db-scheduler from 16.9.0 to 16.10.0 in /service — espoon-voltti/oppivelvollisuus0 reactions
- May 18, 2026build(deps): bump the dependencies group with 21 updates — jooby-project/jooby0 reactions
- May 17, 2026chore(deps): bump the maven-dependencies group across 1 directory with 8 updates — AxonIQ/AxonFramework0 reactions · 1 comment
- May 12, 2026Bump com.github.kagkarlsson:db-scheduler from 16.8.1 to 16.9.0 in /spring-boot-containers — muzir/softwareLabs0 reactions
- May 12, 2026Bump com.github.kagkarlsson:db-scheduler from 16.7.1 to 16.9.0 — quarkiverse/quarkus-db-scheduler0 reactions · 1 comment
- May 11, 2026build(deps): bump the dependencies group with 14 updates — jooby-project/jooby0 reactions
- May 10, 2026chore(deps): bump the maven-dependencies group across 1 directory with 10 updates — AxonIQ/AxonFramework0 reactions · 1 comment
- May 7, 2026Bump com.github.kagkarlsson:db-scheduler from 16.7.1 to 16.8.1 in /spring-boot-containers — muzir/softwareLabs0 reactions
- May 7, 2026Bump com.github.kagkarlsson:db-scheduler from 16.7.1 to 16.8.1 — quarkiverse/quarkus-db-scheduler0 reactions · 1 comment
- Apr 29, 2026Update dependency com.github.kagkarlsson:db-scheduler to v16 - autoclosed — MyBorislavrOrg/qubership-core-process-orchestrator0 reactions
- Feb 3, 2026Bump com.github.kagkarlsson:db-scheduler from 16.6.0 to 16.7.0 — navikt/veilarbportefolje0 reactions · 1 comment
- Feb 3, 2026Bump com.github.kagkarlsson:db-scheduler from 16.6.0 to 16.7.1 in /spring-boot-containers — muzir/softwareLabs0 reactions · 3 comments
- Jan 16, 2026Update dependency com.github.kagkarlsson:db-scheduler to v16 — MyBorislavrOrg/qubership-core-process-orchestrator0 reactions
- Jan 16, 2026Update minor dependencies — MyBorislavrOrg/qubership-core-process-orchestrator0 reactions
- Jan 7, 2026refactor(scheduler): upgrade to db-scheduler Spring Boot 4 starter — arunderwood/nextskip0 reactions
- Jan 6, 2026Bump com.github.kagkarlsson:db-scheduler from 16.6.0 to 16.7.0 in /spring-boot-containers — muzir/softwareLabs0 reactions · 1 comment
- Dec 31, 2025fix(scheduler): add manual db-scheduler config for Spring Boot 4 — arunderwood/nextskip0 reactions · 1 comment
- Nov 10, 2025Bump com.github.kagkarlsson:db-scheduler from 16.4.1 to 16.6.0 — navikt/veilarbportefolje0 reactions · 1 comment
- Nov 1, 2025Bump com.github.kagkarlsson:db-scheduler from 15.4.0 to 16.4.1 — Netroforge/authronom-backend0 reactions
On Stack Overflow · 5
- Dec 19, 2015Is Spring's built in Scheduler persistent.?13 votes
- Dec 19, 2015looking for persistent timers for a spring application2 votes
- Dec 18, 2023Cant serialize the Job class while Scheduling due to bean injection1 vote
- Dec 20, 2021Using chaos-monkey-spring-boot together with db-scheduler: getting BeanDefinitionOverrideException1 vote · 1 answer
- May 12, 2021Spring - run @Scheduled dynamically n times0 votes
On Hacker News · 2
- Nov 21, 2018Show HN: db-scheduler – a simple cluster-friendly task-scheduler for Java7 points
- Aug 8, 2019Db-scheduler, a simple cluster-friendly task scheduler gets Spring Boot support2 points
In this repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- pre-prSkill
- schema-changeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 11
Combined PR: every test-scoped dependency, build plugin, example-module dependency and GitHub Action, all in one PR.
- Distinctive: line 93
If a bump breaks the build, drop it and list it under "Not included" with the error.
- Distinctive: line 114
If a run fails because of one bump, drop that bump, push a new commit (never force-push), and list it under "Not included" with the failing …
- Very specific: line 119
Use the open-pr skill: preview, wait for approval, open as --draft.
- Distinctive: line 150
Write "Supersedes" only for a dependabot PR whose every update is covered across the PRs you open.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Consolidate dependency bumps
Turn open dependabot PRs plus other available minor/patch updates into a few draft PRs:
- Combined PR: every test-scoped dependency, build plugin, example-module dependency and GitHub Action, all in one PR.
- Runtime PRs: dependencies that ship to users go in separate PRs, one per family: Spring Boot, jackson (2.x + 3.x), gson, micrometer, cron-utils, jspecify, slf4j.
Precedent: #962 (combined) and #963 (Spring Boot).
1. Collect
git checkout master && git pull --ff-only # local master is often behind
gh pr list --author app/dependabot --state open --json number,title,headRefName
gh pr diff <n> | grep -E '^[-+] |^\+\+\+' # exact old -> new for each PRThen scan for Maven updates dependabot hasn't filed yet. Run the scans one after the other (~2 min). Scan once without majors and once with them, so a newer minor isn't hidden behind a major:
MVN=$(command -v mvn || ls -d ~/.m2/wrapper/dists/apache-maven-*/*/bin/mvn | tail -1)
V=org.codehaus.mojo:versions-maven-plugin:2.18.0
for MAJ in false true; do
$MVN -B $V:display-dependency-updates $V:display-plugin-updates \
-DprocessDependencyManagement=false -DallowMajorUpdates=$MAJ \
-Dmaven.version.ignore='(?i).*(alpha|beta|milestone|rc|cr|preview|snapshot|-m\d+|\.M\d+|-ea|-jdk5).*' \
2>&1 | grep -E -- '->|Building' | sed 's/\[INFO\] *//' | awk '!s[$0]++'
doneThe scan reports effective versions. Find where each version is actually
declared (a root pom.xml property, db-scheduler/pom.xml, or an inline
<version>) and edit it there. display-property-updates misses the root
properties that feed BOM imports, so don't rely on it.
GitHub Actions versions come only from dependabot PRs; the scan doesn't cover them.
2. Classify each candidate
Runtime means: declared in a published module (db-scheduler, db-scheduler-spring-*)
with no <scope>, or with scope compile/runtime, including <optional>true.
BOM imports count by what they manage (jackson-bom → jackson).
| Candidate | Action |
| Runtime dependency, minor/patch | Runtime PR for its family |
| Test-scoped dependency, plugin, examples-only dependency, GitHub Action (minor/patch) | Combined PR |
| Any major, including one dependabot proposed | Don't apply. List under "Not included" |
| Dependabot proposes a major, and the scan shows a newer minor in the current major (mariadb 4.0.0 vs 3.5.11) | Apply the minor; list the major |
Dependency with no <version> in starters/examples (Spring Boot BOM: micrometer, junit, hsqldb, logback) | Skip. It follows Spring Boot |
slf4j.version 1.7.x, logback.version 1.2.x in core | Skip. Pinned on purpose |
com.github.kagkarlsson:db-scheduler self-reference | Skip |
Scan suggests a different suffix (.jre8 → .jre11, -jdk5) | Keep the repo's suffix; bump the number only |
3. Apply and verify
One branch per PR, each off fresh master: deps/consolidate-bumps-YYYY-MM-DD,
deps/<family>-YYYY-MM-DD. Edit with Edit or sed, then run:
$MVN -B spotless:apply license:format
$MVN -B install -DskipTests -DskipChecks # puts every module in ~/.m2 so -pl works without -am
for M in <modules>; do # one module at a time; memory is tight
$MVN -B verify -pl $M 2>&1 | grep -E 'Tests run:.*Fail|BUILD|\[ERROR\]' | grep -v ' -- in ' | tail -5
doneModules:
- Combined PR:
db-scheduler,examples/features,examples/spring-boot-example, plus every starter module listed below. - Spring Boot PR: the starter modules and
examples/spring-boot-example. - Other runtime PRs:
db-schedulerand the starter modules.
Starter modules, under db-scheduler-spring-boot-starter-parent/:
db-scheduler-spring-common, db-scheduler-spring-boot3-starter, db-scheduler-spring-boot4-starter.
The Boot 4 starter logs Expected one execution to be updated, but updated 0.
That is expected noise from its per-test truncate. Judge by Tests run and
BUILD SUCCESS.
If a bump breaks the build, drop it and list it under "Not included" with the error. Don't fix source code in a deps PR.
git diff touches only pom.xml files and .github/workflows/*. If spotless
changed source files after a formatter bump, put that in its own commit:
style: apply <plugin> <version> formatting.
4. Push and wait for CI
Pushing a branch runs build (full -Ptests-for-ci with the Docker compatibility
tests that can't run locally) and spring-boot-compatibility. Each takes about 5
minutes. Push every branch, then wait for both workflows to finish before
previewing any PR:
git push -u origin "$B:$B"
gh run list --branch "$B" --event push --json databaseId,workflowName,status,conclusion
gh run watch <databaseId> --exit-status # run in background; one per workflow
gh run view <databaseId> --log-failed | tail -50 # on failureIf a run fails because of one bump, drop that bump, push a new commit (never force-push), and list it under "Not included" with the failing test.
5. PR
Use the open-pr skill: preview, wait for approval, open as --draft. The
branches are already pushed, so open-pr only runs gh pr create. Preview all
the PRs together so they can be approved in one go.
Titles must pass the semantic-PR lint:
- Combined:
build(deps): consolidate dependency bumps - Runtime:
build(deps): bump <family> to <version>
Body shape. Each paragraph is a single line; don't hard-wrap. Use only these parts, in this order, and drop any part that would be empty:
- One sentence: what it bumps or replaces, and
Supersedes #a, #b. - Bullets of
artifact from -> to, grouped by kind (test drivers/tooling, plugins, actions). Not included: <artifact> <to> (<major | build failure>).Verified with mvn verify on <modules> locally and a green CI run on the branch.---thenThis PR was prepared with Claude Code.
Example (runtime PR):
Bumps the Spring Boot 4 starter from 4.0.9 to 4.1.2 (minor release).
- spring-boot-4.version 4.0.9 -> 4.1.2
Verified with `mvn verify` on spring-common, both starters and the spring-boot example locally and a green CI run on the branch.
---
This PR was prepared with Claude Code.Write "Supersedes" only for a dependabot PR whose every update is covered across the PRs you open. If something from it was left out (a major), write "partially covers #n". Never close dependabot PRs yourself; dependabot closes them once master has the versions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

