You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a Nix and Renovate user, I am frustrated when Nix Docker image update merge requests show up with no useful information about what changed. There's no indication whether the update is important (such as a security fix), or how to find more information. A quick search of the repo main page shows no relevant hits for words like "release" and "change".
I was able to find some release information like this:
Search for "nix versions" - the only relevant hit on the first screen seems to be a third party one from 2020.
Search for "nix releases" - shows a link to the 2.22 release as the first hit. It looks like the "latest" link is not being prioritised by search engines.
Manually replace "2.22" in the URL with "latest" on a whim, which redirects to the latest index where I can find the link to the latest release.
Notice that there doesn't seem to be any release notes for patch releases, such as 2.25.2.
Describe the solution you'd like
A web feed (Atom seems to be the go-to solution these days) would be useful to be able to keep track of releases in almost real time.
Change log entries compatible with Renovate would enable much more useful merge request descriptions.
Is your feature request related to a problem? Please describe.
As a Nix and Renovate user, I am frustrated when Nix Docker image update merge requests show up with no useful information about what changed. There's no indication whether the update is important (such as a security fix), or how to find more information. A quick search of the repo main page shows no relevant hits for words like "release" and "change".
I was able to find some release information like this:
Describe the solution you'd like
Priorities
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: