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

Update .shasum file check for unzipping binary #806

Merged
merged 3 commits into from
Oct 2, 2019
Merged

Conversation

designatednerd
Copy link
Contributor

@designatednerd designatednerd commented Oct 2, 2019

This PR addresses something brought up a couple times, including in #805: Right now we're checking the output of shasum, which is the actual SHASUM plus the full, hard-coded path used to create it. That doesn't help much if this file is checked into version control, which it would be if a developer checks in all their CocoaPods.

To address this, I've:

  • Updated the check of the .shasum file to only look at the prefix, ie the actual SHASUM and not the path, for anyone with an existing .shasum file.
  • Updated the creation of the .shasum file to not write out the path in the future.

Edit: I also snuck in a change to make sure the local node binary included with Apollo is preferred to any other node version installed, which also should make sure there are no issues if no version of node is globally installed on a developer's computer.

@designatednerd designatednerd merged commit b917a75 into master Oct 2, 2019
@designatednerd designatednerd deleted the update/sha branch October 2, 2019 23:36
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.

1 participant