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

Nupkg path in RELEASES file gets updated incorrectly #59

Open
daviwil opened this issue Jun 10, 2018 · 5 comments
Open

Nupkg path in RELEASES file gets updated incorrectly #59

daviwil opened this issue Jun 10, 2018 · 5 comments

Comments

@daviwil
Copy link

daviwil commented Jun 10, 2018

I noticed something weird when I started producing deltas for releases using the update service as the remoteReleases URI in electron-winstaller. It seems that the update service is returning this for the latest release's RELEASES file now:

9A410F776059D4CEA85D008B461D90C7B95033EB https://github.com/atom/atom-nightly-releases/releases/download/1.29.0-nightly6/https://github.com/atom/atom-nightly-releases/releases/download/1.29.0-nightly5/atom-1.29.0-nightly5-full.nupkg 149089622
B6E8F9C8D6BE42E7888EE35CF90C4C4C10C0DB28 atom-1.29.0-nightly6-delta.nupkg 48698787
B503279BD722E84E74F611AFBF4E3F2DE60F48CD atom-1.29.0-nightly6-full.nupkg 149087747

On the first line, the nupkg path is double-prefixed with a URL path. The original RELEASES file from my repo looks like this:

9A410F776059D4CEA85D008B461D90C7B95033EB https://github.com/atom/atom-nightly-releases/releases/download/1.29.0-nightly5/atom-1.29.0-nightly5-full.nupkg 149089622
B6E8F9C8D6BE42E7888EE35CF90C4C4C10C0DB28 atom-1.29.0-nightly6-delta.nupkg 48698787
B503279BD722E84E74F611AFBF4E3F2DE60F48CD atom-1.29.0-nightly6-full.nupkg 149087747

This could be the consequence of using a different repository for delivering releases, perhaps Squirrel is doing something sneaky there?

@juliangruber
Copy link
Contributor

juliangruber commented Jun 11, 2018

I copied our RELEASES prefixing code from https://github.com/zeit/hazel/blob/master/lib/cache.js#L45-L55, hoping that since hazel has had good use it would be correct.

You can also see tests for this current logic here and here.

For the reference, this are the original RELEASE files' contents, before the update server modifies it:

Nightly5:

9A410F776059D4CEA85D008B461D90C7B95033EB atom-1.29.0-nightly5-full.nupkg 149089622

Nightly6:

9A410F776059D4CEA85D008B461D90C7B95033EB https://github.com/atom/atom-nightly-releases/releases/download/1.29.0-nightly5/atom-1.29.0-nightly5-full.nupkg 149089622
...

@juliangruber
Copy link
Contributor

@davej how does that URL make it into your Nightly6 RELEASE file?

@davej
Copy link

davej commented Jun 11, 2018

@juliangruber: wrong Dave you've mentioned 🙂

@juliangruber
Copy link
Contributor

oops @daviwil

@mahnunchik
Copy link

It seems this issue is exactly related to electron/electron#24149

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

No branches or pull requests

4 participants