Skip to content

https://nodejs.org/download/release/index.* not updated for Node 21.2.0 #72

Closed

Description

@Conduitry

URL:

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

Browser Name:

n/a

Browser Version:

n/a

Operating System:

n/a

How to reproduce the issue:

The https://nodejs.org/download/release/index.json and https://nodejs.org/download/release/index.tab files were not updated to include Node 21.2.0 that was released earlier today.

I do note that https://nodejs.org/dist/index.json and https://nodejs.org/dist/index.tab were updated.

Is this a bug in the release process? Are the old URLs deprecated and should they redirect to the /dist/ ones?

Should I update scripts that are currently using https://nodejs.org/download/release/index.tab to use https://nodejs.org/dist/index.tab instead?

Activity

  1. ovflowd commented on Nov 15, 2023

    @ovflowd
    Member

    Too many assumptions here, but fair process of thought. No, nothing is wrong; We're making some tests in our infrastructure and switching traffic from our DigitalOcean server to Cloudflare R2 + Cloudflare Workers.

    The /download/ path was being served by R2 whilst /dist is still being served by DO. We changed /download for the time being to be served once again by DO until we fix some of the current issues.

    You can see the progress on https://github.com/nodejs/release-cloudflare-worker

  2. transferred this issue fromnodejs/nodejs.orgon Nov 15, 2023
  3. ovflowd commented on Nov 15, 2023

    @ovflowd
    Member

    Also, kinda worrying that these paths were not updated, but I'm assuming that we have an issue where for some reason the promote script didn't promote them.

    @targos is there any log from the promote script execution you can provide? @flakey5 asked if the upload_to_cloudflare.sh was called or not 🤔

  4. targos commented on Nov 15, 2023

    @targos
    Member

    There were no relevant logs.

  5. richardlau commented on Nov 15, 2023

    @richardlau
    Member

    @flakey5 asked if the upload_to_cloudflare.sh was called or not 🤔

    It must have been called for the release assets to have been uploaded to R2, right?

  6. targos commented on Nov 15, 2023

    @targos
    Member

    I manually synced the assets after seeing that they were not on R2

  7. targos commented on Nov 15, 2023

    @targos
    Member

    I don't know if the upload script was called, but it isn't commented out in _promote.sh:
    CleanShot 2023-11-15 at 14 49 02

  8. ovflowd commented on Nov 15, 2023

    @ovflowd
    Member

    I don't know if the upload script was called, but it isn't commented out in _promote.sh: CleanShot 2023-11-15 at 14 49 02

    Not even sure if this logic is correct. @MoLow was the one that initially implemented it, right?

  9. MoLow commented on Nov 16, 2023

    @MoLow
    Member

    yes, it seems correct.

  10. ovflowd commented on Nov 16, 2023

    @ovflowd
    Member

    Can we simulate this script for v21.2.0 to see what it does? (what are the args that it passes?)

  11. MoLow commented on Nov 23, 2023

    @MoLow
    Member

    this seems to have been updated

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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions