chain-registry is not up-to-date #9
Comments
odeke-em
added a commit
that referenced
this issue
Oct 15, 2022
…ccurate
This change implements functionality to retrieve the latest
go.mod from the live Github repository. It also requires that
the spreadsheet have 2 different sheets "Projects" & "LatestProjects"
The only problem is that we quickly hit Github API quotas with messages like:
```
error="{\"message\":\"API rate limit exceeded for [REDACTED]. (But here's the
good news: Authenticated requests get a higher rate limit. Check out the documentation
for more details.)\",\"documentation_url\":\"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting\"}\n"
org_repo=/vidulum/mainnet
```
Updates #9
odeke-em
added a commit
that referenced
this issue
Oct 16, 2022
odeke-em
added a commit
that referenced
this issue
Oct 16, 2022
This code uses the always live Github version of each repository because sadly the content on the chain-registry is heavily unmaintained. This change performs a shallow git clone to only get the default branch from `.git/HEAD` => `/refs/<DEFAULT_BRANCH>` to then go fetch the live code. It is so much better to get the live data that try to guess what was deployed and in the chain registry since we've got deadlinks like: * https://github.com/imversed/imversed Fixes #9
odeke-em
added a commit
that referenced
this issue
Oct 16, 2022
This code uses the always live Github version of each repository because sadly the content on the chain-registry is heavily unmaintained. This change performs a shallow git clone to only get the default branch from `.git/HEAD` => `/refs/<DEFAULT_BRANCH>` to then go fetch the live code. It is so much better to get the live data that try to guess what was deployed and in the chain registry since we've got deadlinks like: * https://github.com/imversed/imversed Fixes #9
odeke-em
added a commit
that referenced
this issue
Oct 16, 2022
This code uses the always live Github version of each repository because sadly the content on the chain-registry is heavily unmaintained. This change performs a shallow git clone to only get the default branch from `.git/HEAD` => `/refs/<DEFAULT_BRANCH>` to then go fetch the live code. It is so much better to get the live data that try to guess what was deployed and in the chain registry since we've got deadlinks like: * https://github.com/imversed/imversed Fixes #9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can get the repo from the chain-registry but the version it reports is often out of date.
Can we instead get the latest release from the chain's repo and get the versions based on that ?
I guess no method is going to be 100% accurate depending on dev practices. There's no real way to automate this because we don't know when versions get deployed.
Maybe we can just show the output from both ?
The text was updated successfully, but these errors were encountered: