Skip to content

Prepare for v27 #1187

Open
Open

Description

@RafaelGSS

Pull requests needed to prepare the v27.x release line. The first Alpha, v27.0.0-alpha.0.0.0, is planned for 2026-10-28.

These are all the changes I could map. If I missed something, please let me know in this issue.

cc @nodejs/releasers

Activity

  1. MikeMcC399 commented on Oct 18, 2026

    @MikeMcC399
    Member
  2. joyeecheung commented on Oct 19, 2026

    @joyeecheung
    Member

    I am working on a V8 14.6 (on 26) -> 15.6 (on main currently) highlights for the release notes, it's still currently incomplete. https://hackmd.io/@openjs-nodejs/Bkrj9UAjMg

    Note that V8 15.6 will have a stable release on Oct 20 (which would include bug fixes etc. they catch from Chrome). I'll refresh the V8 version on main then, and it shouldn't have much build issues. I think it would be great if 27 ship with that stable release. Planning to finalize the V8 hightlights after that update.

  3. MikeMcC399 commented on Oct 26, 2026

    @MikeMcC399
  4. RafaelGSS commented on Oct 27, 2026

    @RafaelGSS
    MemberAuthor

    Created v27.x and v27.x-staging from main (98dbf6070e8) and the v27.x labels (v27.x, backport-blocked-v27.x, backport-open-v27.x, backport-requested-v27.x, backported-to-v27.x, dont-land-on-v27.x)

  5. 4 remaining items

  6. MikeMcC399 commented on Nov 2, 2026

    @MikeMcC399
    Member

    Please open a Release plan issue for Node.js 27, like for #1152 so that downstream consumers know what to expect. I'm assuming a 2 week cadence on Node.js 27 Alpha releases, but I don't know if that is the plan or not.

  7. richardlau commented on Nov 2, 2026

    @richardlau
    Member

    Please open a Release plan issue for Node.js 27, like for #1152 so that downstream consumers know what to expect. I'm assuming a 2 week cadence on Node.js 27 Alpha releases, but I don't know if that is the plan or not.

    I think that might be waiting on #1193 to generate the schedule.

  8. richardlau commented on Nov 2, 2026

    @richardlau
    Member

    Please open a Release plan issue for Node.js 27, like for #1152 so that downstream consumers know what to expect. I'm assuming a 2 week cadence on Node.js 27 Alpha releases, but I don't know if that is the plan or not.

     I think that might be waiting on [#1193](https://github.com/nodejs/Release/pull/1193) to generate the schedule.
    

    Not just that. Opened #1197.

  9. MikeMcC399 commented on Nov 2, 2026

    @MikeMcC399
  10. MichaIng commented on Nov 3, 2026

    @MichaIng

    Is it intended that the alpha version appears in index.tab? I thought that was for (stable) releases only?

    https://nodejs.org/download/release/index.tab

  11. aduh95 commented on Nov 16, 2026

    @aduh95
    Contributor

    I wonder if we could come up with a rule to include semver-major changes only in a few Alpha releases, so hopefully there's no longer a need to differentiate Alpha and Current releases. Maybe 2 months would be the right tradeoff (the more the 27 branch deviates from main, the higher the maintenance burden; hopefully 2 months is not enough time for the deviation to be painful).
    So far we haven't included any semver-major changes in our Alpha versions (well except the very first one, obviously), and I haven't encountered any conflicts so far.

  12. ljharb commented on Nov 16, 2026

    @ljharb
    SponsorMember

    why would we not want them differentiated? the entire point of alphas is for people who want to try unstable, bleeding-edge code. If it's not something that should never be used in production, then "alpha" is the wrong name for it.

  13. aduh95 commented on Nov 16, 2026

    @aduh95
    Contributor

    We want library authors to test with them. "alpha" might be the wrong name for it, what we're aiming for is for LTS to be for production, and Current and Alpha to be tested by library authors (to catch bugs/breakage before they reach LTS/production)

  14. ljharb commented on Nov 16, 2026

    @ljharb
    SponsorMember

    right - but alphas still should never go into production, and the vast majority of node users (who are not library authors) should actively be avoiding alphas.

  15. MichaIng commented on Nov 16, 2026

    @MichaIng

    Basically setting "alpha" and "current" (latest stable release) equal seems weird, same like the fact that alpha versions are listed in https://nodejs.org/download/release/index.tab, where I would expect actual "releases", no alpha/beta/rc. https://github.com/nodejs/unofficial-builds/blob/main/www/install-node.sh also pulls the alpha versions now. Of course this can be all adjusted, but needs to be communicated.

  16. aduh95 commented on Nov 16, 2026

    @aduh95
    Contributor

    Alpha are actual releases. The same care goes into preparing a Alpha release and a Current release, it's the same process, the same tests are run, etc. The difference is the semver guarentees.

    right - but alphas still should never go into production, and the vast majority of node users (who are not library authors) should actively be avoiding alphas.

    I don't think the vast majority of users are running on production, so I don't think they need to avoid Alpha more than Current

  17. MichaIng commented on Nov 16, 2026

    @MichaIng

    Okay, then "alpha" is the entirely wrong name, indeed. But good to know.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions