Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node-gyp@5.1.0 Release Proposal #2012

Closed
wants to merge 16 commits into from
Closed

node-gyp@5.1.0 Release Proposal #2012

wants to merge 16 commits into from

Conversation

rvagg
Copy link
Member

@rvagg rvagg commented Jan 3, 2020


This is mainly a backlog flushing exercise, as you can see, almost everything is docs or test, but there is also #1978 which hasn't yet been released on master so the choice is:

  1. let this simmer until it's out on a v6.x release and has had time in the wild
  2. remove it from this release and just flush out a doc update release
  3. yolo, just release it

Will opt for 1 at the moment, it's mainly just interesting to see what the diff is. Feel free to weigh in.

rvagg and others added 12 commits December 16, 2019 11:59
Republish of v5.0.6 but with node-gyp-v5.0.6.tar.gz removed from pack file

PR-URL: #1972
PR-URL: #1971
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
PR-URL: #1985
Reviewed-By: Christian Clauss <cclauss@me.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Running Python standalone tests on multiple OSes would free up Travis CI for tests of various combinations of Node.js and Python as well as tests on other [CPU architectures](https://docs.travis-ci.com/user/multi-cpu-architectures).  __arch: amd64, arm64, ppc64le, s390x__

PR-URL: #1985
Reviewed-By: Rod Vagg <rod@vagg.org>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Uses `pyenv` to manage MacOS python versions since its not included
in the environment.

rvagg: landing this from #1979 even though it wasn't from the original
author. Treating approval there as approval of this commit too.

PR-URL: #1979
Reviewed-By: Rod Vagg <rod@vagg.org>
Reorder Travis builds by OS. Replace `pyenv global` calls with
properly set `PATH` and `PYENV_VERSION` env vars. Does not
assume python modules are in the `PATH` so all python
modules are prefixed with `python -m`.

PR-URL: #1979
Reviewed-By: Christian Clauss <cclauss@me.com>
Reviewed-By: Rod Vagg <rod@vagg.org>
PR-URL: #1978
Reviewed-By: Rod Vagg <rod@vagg.org>
PR-URL: #2001
Reviewed-By: Christian Clauss <cclauss@me.com>
Reviewed-By: Rod Vagg <rod@vagg.org>
PR-URL: #1996
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
PR-URL: #1992
Reviewed-By: Christian Clauss <cclauss@me.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
PR-URL: #1993
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
PR-URL: #1994
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Christian Clauss <cclauss@me.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
@richardlau
Copy link
Member

I’m okay with any of the three options but I do wonder how much in the wild exposure 6.x gets since it isn’t used by npm.

@imatlopez
Copy link
Contributor

imatlopez commented Jan 9, 2020

@rvagg was about to ask you if the no proxy support was making it to v5 (I see that it is)

In order to be used at our company it will need to get to node at some point and the only way is through npm which uses v5 :(

@rvagg
Copy link
Member Author

rvagg commented Jan 10, 2020

@imatlopez yep, it'll go in, I just want it to bake in the wild in v6 first. That's been out for a couple of days but we should give it a couple of weeks at least to be sure (similar practice in Node.js itself for backporting is a couple of months, minimum). We have to be more careful shipping potentially breaking features in v5 since it's got a significantly larger userbase (also I don't want to be personally responsible for people screaming at npm).

cclauss and others added 4 commits February 3, 2020 14:43
Fixes #1998

Reviewed-By: Rod Vagg <rod@vagg.org>
PR-URL: #2009
Fixes: #2005
Reviewed-By: Rod Vagg <rod@vagg.org>
PR-URL: #2006
I have quite a few instances of VS installed and it looks like
Find-VisualStudio.cs enumerates all of them, even when
find-visualstudio.js already knows which one it wants (from the
environment variable in the developer command prompt).  One of them
(from 15.7.2, if that's interesting) causes a COMException on the
ISetupInstance2.GetPackages call.  Ignoring such packages seems
harmless and unblocks the rest of the run.

PR-URL: #2018
Reviewed-By: João Reis <reis@janeasystems.com>
@rvagg
Copy link
Member Author

rvagg commented Feb 3, 2020

Speak up now if you have anything that should hold up a release.

Synced with master, updated OP and prepared package.json and CHANGELOG.md for a release tomorrow.

This puts v5 roughly in sync (minus semver-major) with v6.1.0 but also adds #2018 because that seems pretty safe and has been waiting for a new v6 release.


For the record, this is the diff with master:

  • [d1dea13fe4] - doc: fix changelog 6.1.0 release year to be 2020 (Quentin Vernot) #2021
  • [a79d866ac3] - v6.1.0: bump version and update changelog (Rod Vagg) #2013
  • [9a7dd16b76] - doc: remove backticks from Python version list (Rod Vagg) #2011
  • [68319a2c34] - v6.0.1: bump version and update changelog (Rod Vagg) #1935
  • [1a4ff636d5] - v6.0.0: bump version and update changelog (Rod Vagg) #1892
  • [dd0e97ef0b] - (SEMVER-MAJOR) lib: try to find python after python3 (Sam Roberts) #1907
  • [f60ed47d14] - travis: add Python 3.5 and 3.6 tests on Linux (Christian Clauss) #1903
  • [c763ca1838] - (SEMVER-MAJOR) doc: Declare that node-gyp is Python 3 compatible (cclauss) #1811
  • [3d1c60ab81] - (SEMVER-MAJOR) lib: accept Python 3 by default (João Reis) #1844
  • [c6e3b65a23] - (SEMVER-MAJOR) lib: raise the minimum Python version from 2.6 to 2.7 (cclauss) #1818

@rvagg rvagg closed this Feb 5, 2020
@rvagg rvagg deleted the v5.1.0-proposal branch February 5, 2020 02:19
rvagg added a commit that referenced this pull request Feb 5, 2020
rvagg added a commit that referenced this pull request Feb 5, 2020
@rvagg
Copy link
Member Author

rvagg commented Feb 5, 2020

published v5.1.0

Copy link

@O330oei O330oei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add

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.

10 participants