Change:
''; nextcloud25 = generic { <del> version = "25.0.8"; sha256 = "sha256-Ia6afooDCNDZsGSoh5dddZvLUE3fU+jU6sy6MrxUMVs="; </del> <ins> version = "25.0.9"; sha256 = "sha256-k5XVM0ABRtAiCNoPNvkpYxq16Nb9Xd/VXNpqIDWg/nA="; </ins> packages = nextcloud25Packages; }; nextcloud26 = generic { <del> version = "26.0.3"; sha256 = "sha256-pagQy818Pc/yXyKAkyHy7UHtfMBgEgRImskOJYBgtck="; </del> <ins> version = "26.0.4"; sha256 = "sha256-gBya6RLPYmS+csFB5BjT2H1OZxx6ndZDAI9dfWmR6i4="; </ins> packages = nextcloud26Packages; }; nextcloud27 = generic { <del> version = "27.0.0"; sha256 = "sha256-PTEqCbk0WsBYdY3XtAWb888LHw8ddHJRtvrDWFumUz8="; </del> <ins> version = "27.0.1"; sha256 = "sha256-OXa16PWPk03b63zEmsM7Ea0629f21dCQig/DahYMJ70="; </ins> packages = nextcloud27Packages; };

Discussion:
Package name: nextcloud{27,26,25} Latest released version: 27.0.1 <!-- Search your package here: --- Current version on the unstable channel: 27.0.0 Current version on the stable/release channel: 27.0.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Other releases were made for major version 25 and 26 : ! On unstable : ! On 23.05 release channel : ! Note for maintainers: Please tag this issue in your PR.
I'd like to work on a GitHub Actions that automatically, bumps the version if it is just a minor version bump, is that something possible ?
While I think we have GH Actions for a very small subset of packages, I'm not a big fan of multiple infrastructures for upgrading packages considering that we also have Also, when merging a Nextcloud update it's always a good idea for $maintainer to actually deploy this to a live instance for testing, so manual intervention is needed anyways and I don't consider the version bump that much of an additional burden %)
I agree with you, major version bumps should be thoroughly tested by someone with manual intervention, however for minor version such as all bumps in 27.y.x, I don't think there is a very big risk for something to break, if there are some integration test running before merging is done. Also, this GitHub Actions/or using any bot could have the sole purpose of only notifying maintainers of a new version available. I don't know if it is possible using as I'm totally not familiar with the automatic workflows that are run in Nixpkgs. For instance, an automatic issue to bump the version be created if and only if the issue doesn't exist and the version inside the master branch of Nixpkgs is older than the new release.

EDIT : I'm fine using the available infrastructure or recommended one to try and do just that as far as I can get help if there is any non documented process I need to go through
You will find the documentation here: I very much agree with that ideally all versions bumps should be tested on a live instance.
Also FYI you don't need to paste screenshots for outdated versions, we believe you without them
No worries for the screenshots, I'll put text next time, I was just a bit lazy not really concerned about whether you'd believe or not
Next time, consider sending a PR, it will go faster ;).