-
Notifications
You must be signed in to change notification settings - Fork 77
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
Comments
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 Nightly5:
Nightly6:
|
@davej how does that URL make it into your Nightly6 RELEASE file? |
@juliangruber: wrong Dave you've mentioned 🙂 |
oops @daviwil |
It seems this issue is exactly related to electron/electron#24149 |
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:On the first line, the nupkg path is double-prefixed with a URL path. The original RELEASES file from my repo looks like this:
This could be the consequence of using a different repository for delivering releases, perhaps Squirrel is doing something sneaky there?
The text was updated successfully, but these errors were encountered: