Eleven PRs in one afternoon — the day the bot became a teammate
Portfolio·

Eleven PRs in one afternoon — the day the bot became a teammate

On Wednesday I opened the Portfolio repository and the pull request queue looked like an auction: eleven dependabot PRs stacked up, each with the same polite request — “bump X from A to B”. In projects I maintained in the past, that queue meant a lost afternoon: reading changelogs by hand, running the build, crossing fingers. This time the process was different, and the difference wasn’t luck.

What came in the batch

PackageFromTo
vercel58.9.059.11.7
vitest4.1.105.0.0
framer-motion13.0.013.2.0
mercadopago3.3.03.6.0
eslint-config-next16.3.016.3.4
@testing-library/user-event14.6.314.6.7
@testing-library/jest-dom6.9.17.0.1
@testing-library/react16.3.216.3.3
@vitejs/plugin-react6.0.56.1.1
netlify-cli27.1.127.5.0
actions/setup-pythonv6v7

Most of the batch is what I call invisible polishing: deploy CLIs, lint configs, testing bindings. None of these ship in the bundle the user downloads. The real risk concentrates in two spots: vitest, which jumped a major version (4 to 5), and framer-motion, which controls the animation of everything that moves on the home page.

The tools I use on this project live in the skills store — the first one is free.

The major that didn’t hurt

A test runner major is usually the scariest PR in the queue — it’s the package that decides whether CI stays green. Vitest 4.1.10 to 5.0.0 came in as PR #77 and passed without a single change to the test code. That’s not the dependabot’s merit, it’s the merit of technical debt I never took on: the project uses no experimental runner APIs, no obscure plugins, no exotic configuration. The rule I learned maintaining this repository: the duller your testing dependencies, the cheaper the major.

The framer-motion snapshot false alarm

Framer-motion 13.2.0 (PR #78) came at the end of the queue and became the last merge of the day. And in the same week, a visual regression test run failed with a 6% diff against a 5% budget. First-hour instinct: “the update broke something”.

Except the same test, run again against an identical build with frozen baselines, passed without a single pixel of difference. The 6% diff was animation timing — a frame captured in a different phase of the transition — not a visual regression. Framer-motion is the most alive package on the home page: it animates entrance, hover and scroll, and any test that photographs the page mid-transition is photographing time, not pixels.

The process that holds the batch

The flow that makes this day possible is simple to describe and expensive to build:

  1. Dependabot opens the PR with a changelog and release link
  2. CI runs the entire suite on the PR branch — unit and E2E tests
  3. Green = merge; red = the PR waits and the investigation happens in isolation
  4. After the batch, an integration commit ties everything into the project’s history

Step 3 is what turns a queue of 11 PRs into routine instead of a gamble. CI is what reads the changelog for me — it doesn’t summarize features, but it answers the only question that matters: does it still work?

PR typeWhat decidesWhat can hurt
CLI patch/minorgreen CInothing, in practice
Test runner majorthe whole suitebroken config, removed API
UI/animation libCI + VRTsnapshot flake, timing

The lesson of the day

The counterintuitive part of keeping dependencies up to date isn’t technical — it’s trust. Trust that CI covers what the changelog doesn’t tell you, and the discipline of never merging a PR the CI hasn’t seen. Eleven PRs in a single afternoon isn’t robot productivity: it’s the result of a project where the safe path is also the fast path.

The batch closed with a green suite and an empty queue. Next round, dependabot will open more — and the queue, again, will be routine.

~/lifelog — bash
$cat about.txt
╔══════════════════════════════════════╗
║  Samuel Medeiros                    ║
║  Senior Software Engineer           ║
║  Stack: Python · TypeScript · Rust  ║
║  Projetos: Arachne, Dogwalk,        ║
║            Capivara, TatuEngine      ║
╚══════════════════════════════════════╝
      
$

Related entries

Same project, same ground — the stories connect.

Next step

If this was useful, there is more: I write about the same ground in the other projects, and the store holds the tools I use here.

No spam, one-click unsubscribe. I am also here: Skills store · Portfolio