justwatchcom / github-releases-notifier Goto Github PK

Awesome tool! Literally stumbled on it when I was searching for something that would monitor releases of gopass. I have this error for a couple of repo's I am following. Is there a standard in the way projects should list releases in order to be followed correctly? Or is this just a warning?

Rename package from githubql to githubv4 - breaking API change.

So this can be executed on a RPI or a pi k8s cluster

Typo in readme example:

kubectl create secret generic github-releases-notifier \ --from-literal=github=XXX
--from-literal=slack=XXX`

Readme secret example missing/partially wrong formatting quoted values.

Do you have a list of which permissions are required for the GitHub API token?

Thanks!

Hi, I wanted you to be aware of a possible issue with shurcooL/githubql's package. Querying for releases is failing a lot. The output when starting your docker image is:

{"caller":"releasechecker.go:40","err":"can't find any releases for angular/angular","msg":"failed to query the repository's releases","name":"angular","owner":"angular","severity":"warn","ts":"2017-11-28T22:03:33.95055614Z"}

Some of the things I've found:

primefaces/primeng, singularityware/singularity seems to work. The following are failing: rstudio/rstudio, angular/angular, pallets/flask, zzzeek/sqlalchemy, rstudio/shiny-server

I haven't investigated githubql package a lot, but it seems like there was a recent (within 24 hours) change to their api.

I just tried this to detect new release of some repository but it didn't work. I noticed that the query

	var query struct {
		Repository struct {
			ID          githubql.ID
			Name        githubql.String
			Description githubql.String
			URL         githubql.URI

			Releases struct {
				Edges []struct {
					Node struct {
						ID          githubql.ID
						Name        githubql.String
						Description githubql.String
						URL         githubql.URI
						PublishedAt githubql.DateTime
					}
				}
			} `graphql:"releases(last: 1)"`
		} `graphql:"repository(owner: $owner, name: $name)"`
	}

always gets the oldest release.

If I changed the query to graphql:"releases(first: 1)" it will get the newest release and everything goes well.

Maybe github inverted the sort direction of graphql api recently?