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

feat: upgrade electron-download to 4.x #12993

Merged
merged 1 commit into from
May 18, 2018
Merged

Conversation

malept
Copy link
Member

@malept malept commented May 18, 2018

This is a breaking change, as it causes the electron module to require Node 4.x (which has been EOL'd anyway).

Upgrading adds features such as a customizable cache location (via the ELECTRON_CACHE environment variable).

Originally merged in #10922 but was reverted because it was going into a version of Electron that did not allow breaking changes.

The main difference between this and #10922 is that I explicitly added the engines directive (which in NPM generates a warning, but in Yarn throws an error).

This should go in the release notes.

This is a breaking change, as it causes the `electron` module to require
Node 4.x (which has been EOL'd anyway).

Upgrading adds features such as a customizable cache location (via the
`ELECTRON_CACHE` environment variable).

Originally merged in #10922 but
was reverted because it was going into a version of Electron that did
not allow breaking changes.
@malept malept added the semver/major incompatible API changes label May 18, 2018
@malept malept requested review from a team May 18, 2018 06:20
@MarshallOfSound
Copy link
Member

This has been on the list for a while, can it slot into 3.x before branch @ckerr ?

Copy link
Contributor

@jkleinsc jkleinsc left a comment

Choose a reason for hiding this comment

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

Looks good to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver/major incompatible API changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants