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

Doesn't work for Github private repo #62

Open
Aarbel opened this issue Apr 13, 2019 · 10 comments
Open

Doesn't work for Github private repo #62

Aarbel opened this issue Apr 13, 2019 · 10 comments

Comments

@Aarbel
Copy link

Aarbel commented Apr 13, 2019

The routes of hazel doesn't seem to work with private repo

DOESN'T WORK

const server = "https://clovis-desktop-hazel-upd.aarbel.now.sh"
const updaterFeedURL = `${server}/update/${process.platform}/${app.getVersion()}`

autoUpdater.setFeedURL(updaterFeedURL);

Error:
Unhandled rejection Error: Cannot find channel "latest-mac.yml" update info: HttpError: 404

Please double check that your authentication token is correct. Due to security reasons actual status maybe not reported, but 404.\n

WORKS

const updaterFeedURL = {
    provider: 'github',
    owner: 'my-team',
    repo: 'my-repo',
    token: 'my-github-token',
}

autoUpdater.setFeedURL(updaterFeedURL);
@KASOGIT
Copy link

KASOGIT commented Jul 11, 2019

Hello, that's certainly mean you're not providing "latest-mac.yml" in your mac release, can u check it out ?

@Aarbel
Copy link
Author

Aarbel commented Jul 11, 2019

I do provide latest-mac.yml

@adhambadr
Copy link

#55

@adhambadr
Copy link

adhambadr commented Jul 26, 2019

just add

URL="https://api.github.com/repos/<my-team>/<my-repo>/releases?access_token=<YOURGITHUBTOKEN>"

@cap10morgan
Copy link

just add

URL="https://api.github.com/repos/<my-team>/<my-repo>/releases?access_token=<YOURGITHUBTOKEN>"

This seems dicey from a security perspective and is really just working around a bug. See #76 for a better fix.

@b-zurg
Copy link

b-zurg commented May 7, 2020

This is amazing. Thanks so much @cap10morgan for this PR.

@leo Is this something you could spare some attention to? It would be a huge benefit for those of us using this amazing project but within the constraints of a private repo without having to maintain our own fork of the project.

Something else to note, as of electron 8.2.5 it seems the parameter of setFeedUrl has changed to an object. e.g. so we might update the documentation to reflect that.

autoUpdater.setFeedUrl({ url: `....` })

backroot added a commit to backroot/hazel that referenced this issue Oct 4, 2020
backroot added a commit to backroot/hazel that referenced this issue Oct 4, 2020
backroot added a commit to backroot/hazel that referenced this issue Oct 4, 2020
backroot added a commit to backroot/hazel that referenced this issue Oct 4, 2020
backroot added a commit to backroot/hazel that referenced this issue Oct 4, 2020
backroot added a commit to backroot/hazel that referenced this issue Oct 4, 2020
@backroot
Copy link

backroot commented Oct 4, 2020

This issue resolve in my pull request #98 .
Example for autoUpdater.ts.

import { autoUpdater } from "electron-updater";

const server = "https://hazel-xxxx.vercel.app";
const feed = `${server}/update/${process.platform}/${app.getVersion()}`;

autoUpdater.setFeedURL(feed);

@cap10morgan
Copy link

This software is abandoned. Beware all ye who enter here.

@Tulipesz
Copy link

This software is abandoned. Beware all ye who enter here.

Nuts and now hazel is abandoned. Any hints of any fork/project to implement autoupdater without needing signed code?

@GitMurf
Copy link

GitMurf commented Oct 20, 2023

This software is abandoned. Beware all ye who enter here.

This is such a bummer! I looked at Nuts and then realized it was abandoned... then looked at Hazel and now finding it appears to be abandoned too?

The most frustrating part is that Electron official docs still recommend both of these as two top options! Anyone have any advice?

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 a pull request may close this issue.

8 participants