Skip to content

Conversation

MylesBorins
Copy link
Contributor

Add sunos:

  • v4.6.2
  • v4.7.0
  • v4.7.1
  • v6.9.2
  • v6.9.3

Add cavaet about shasums

  • v4.7.1
  • v4.7.2
  • v6.9.3

add alternative shasums

  • v4.7.1
  • v6.9.3

While promoting additional platforms for v4.7.1 after the release, the tarballs
on the release server were overwritten and now have different shasums. In order
to remove any ambiguity around the release we have opted to do a semver patch
release, v4.7.2, with no changes.

This includes a number of things

* a cavaet about v4.7.2
* the download link for sunos
* the original shas
* the shas currently found on nodejs.org
the original post did not include the cavaet
While promoting additional platforms for v6.9.3 after the release, the tarballs
on the release server were overwritten and now have different shasums. In order
to remove any ambiguity around the release we have opted to do a semver patch
release, v6.9.4, with no changes.

This includes a number of things

* a cavaet about v6.9.4
* the download link for sunos
* the original shas
* the shas currently found on nodejs.org
@MylesBorins
Copy link
Contributor Author

MylesBorins commented Jan 6, 2017

@nodejs/build can you please comment

specifically I would like sign off on including the duplicate share in v4.7.1 and v6.9.3.

/cc @rvagg

@jbergstroem
Copy link
Member

I think providing both shasum records are the best possible outcome for people being confused (read: getting mismatches).

@MylesBorins MylesBorins merged commit 6be0db3 into nodejs:master Jan 6, 2017
yous added a commit to yous/nodejs-ko that referenced this pull request Feb 7, 2019
yous added a commit to yous/nodejs-ko that referenced this pull request Feb 7, 2019
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.

2 participants