📢 8.0 Planned Changes

Open
#685 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
javascript, node.js
Domain
release

Research direction

This is a planning thread for 8.0, not a scoped change: every section (supported Node.js range, changed APIs, removed functions, dependency updates) is still an empty checkbox. Start by reading the linked 8.0.0 milestone and the v7.0.0 release notes to see what already shipped, then check package.json for the current engines field if you want to propose the Node range update. Nothing here is done until the maintainers agree on which breaking changes go into the major.

Written by the indexing model from the issue text.

Description

type: admin

Starting a list of breaking changes for our next major version. As always, feedback is welcome. At the point where we have enough to justify a new major, we'll plan for a release.

I've also created a 8.0.0 Milestone, to track more formally.

Planned Changes

Supported Node.js versions
  • 2026-06-01: v25 EoL
  • Update supported node range to TBD
Changed APIs
Removed Functions
Dependency Updates
Misc

[!NOTE]
v7 was released 2026-10-23 (release).

Dominant language
JavaScript
Stars
427
Forks
157
Avg merge
1d 2h
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from all-contributors/cli

All issues in all-contributors/cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.