Skip to content

Clear dependabot backlog: Actions + npm group updates - #83

Open
j-atkins wants to merge 5 commits into
mainfrom
dependabot-updates
Open

j-atkins wants to merge 5 commits into
mainfrom
dependabot-updates

Conversation

@j-atkins

Copy link
Copy Markdown
Collaborator

There is a backlog of dependabot PRs. In this PR, I directed an LLM to solve all of them in one branch and generally bring up to date.

@erikvansebille I will leave this PR here, please do feel free to take it over and merge once you've had time to look and check this is how you'd like to handle the backlog 🙂

This is the description from the LLM:

Summary

This PR combines the backlog of dependabot updates into one. It upgrades the GitHub Actions and the npm dependencies, including Next 14→16 and React 18→19. It also makes the small fixes those upgrades needed: a new lint config, building with webpack, and gitignoring next-env.d.ts. Most of the large line count is the regenerated package-lock.json. Chakra UI stays at v2 and ESLint at v9, because their newest versions would break the site.

Included

  • GitHub Actions: checkout 5, setup-node 6, upload-artifact 5, upload-pages-artifact 4, lychee-action 2.7.0
  • npm "dependencies" and "dev-dependencies" groups: Next 16, React 19, etc.
  • feed 5.2.1 (RSS items now include authors)
  • glob, typescript and webpack are already covered by the regenerated lockfile

Differences from the dependabot PRs

  • @chakra-ui/react stays at v2 (v3 is a breaking rewrite and needs its own PR)
  • eslint stays at v9 (the Next plugins don't support v10 yet)
  • dev and build use --webpack (Turbopack rejects the MDX options)
  • Lint moved to a flat config because next lint was removed. This also surfaced a missing Image import in project-card.js, which is fixed.
  • next-env.d.ts is now gitignored (Next 16 regenerates it on every run)

Testing

  • npm run build, npm run lint and npm run dev work locally, and the site was clicked through in the browser (including the blog). The Actions upgrades will only be exercised by CI.

Note also the majority of the (very many) line changes come from the package-lock.json file.

j-atkins and others added 5 commits October 23, 2026 14:59
GitHub Actions:
- actions/checkout 4 -> 5
- actions/setup-node 4 -> 6
- actions/upload-artifact 4 -> 5
- actions/upload-pages-artifact 3 -> 4
- lycheeverse/lychee-action 1.8.0 -> 2.7.0

npm (dependencies and dev-dependencies groups):
- next 14 -> 16, react/react-dom 18 -> 19, eslint 9 -> 10, and the
  other grouped bumps
- @chakra-ui/react held at v2 (v3 is a breaking rewrite)
- build/dev use --webpack since Turbopack rejects the non-serializable
  MDX plugin options in next.config.mjs

The feed, glob, typescript and webpack PRs are already covered by the
existing ranges and the regenerated lockfile.
- Replace .eslintrc with a flat eslint.config.mjs and run eslint directly
  (next lint was removed in Next 16)
- Keep eslint at v9; eslint-config-next plugins do not support v10 yet
- Disable the new react-hooks/set-state-in-effect rule
- Import missing Chakra Image in project-card, escape apostrophe in about,
  drop unused eslint-disable directives
Next 16 regenerates it on every dev/build run with differing paths;
Next now recommends gitignoring it.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant