Updated_at should reflect actual theme updates

[eldondevat]

I was looking at the github cache, and it seems to pull the updated_at element from the github api. That element seems to include any action on the repo, even issues opened by other users, so a "recently updated" theme may actually not have had new commits in years. Would a better "updated_at" value be the date on the latest commit to the default branch of the theme?

[bep]

Would a better "updated_at" value be the date on the latest commit to the default branch of the theme?

We use the author date (or commit date, I'm not sure) for the version we uses (e.g. a tag) as reported by Hugo/Go modules. Which I guess is what you ask for. If you somehow see an old date and you have one or more release tags, it means you need to tag a new version using semver tags (e.g. v1.2.3).

[eldondevat]

Ok, I see, I was just looking at using this json file as a data source since I wanted to filter by some additional criteria when looking at the gallery on the theme site