Forgejo Container Timestamp Support

[Stetsed]

Tell us more.

This is in relation to #37196

I wanted to drop a comment on this because it is something I am experiencing recently where I just set timestamp to optional and manually verify whenever I publish due to the current lacking of this feature. I see gitlab has been discussed in the linked issue, however another one I would ask is forgejo, which in proxy allows codeberg and so forth.(It is also possible it would support gitea due to the API in this case being the same to my knowledge, although I currently do not have a gitea instance to test)

Forgejo has an API endpoint “api/v1/packages/{owner}” or the more specific version “api/v1/packages/{owner}/{type}/{name}/{version}”, and it does provide a “created_at” field that is registry controlled and is not derived from anything else as far as I can tell. This seems to make it a perfect candidate for support from the previous discussions I have read? Seems like to query the age you would want to do “api/v1/packages/(owner would need to somehow be split is a bit of a wrinkle, although it’s just the first part of the package name)/container/(second part of package name)/(newVersion)”, and then taking the “created_at field.

I am honestly still relatively new to renovate, it does seem like currently the discussion though is more about how this should be implemented more globally. Because it seems like the want is to make it possible to use it for more registries. If there is interest I might be able to take a look at this myself, but can’t give any real promises as this is smth I have little experience with. As I also see the current plan to implement it for ghcr.io(although this shouldn’t run into those issues specifically as far as I can tell)

[Stetsed]

Note: I originally attached this to the issue I referenced, as I noticed that the discussion in there surrounded a similar topic, but decided to turn it into an actual discussion. If this was wrong and I should have put it there after all I do apologize