I think it's not a big problem to leave this in, but it's not needed. abra recipe release will update this label and make sure it matches the release tag.
I think it's not a big problem to leave this in, but it's not needed. `abra recipe release` will update this label and make sure it matches the release tag.
This line could be a bit higher in the release notes? It's of course not an ordered task list, but to me it makes sense to read this before the 'after deploying' line.
This line could be a bit higher in the release notes? It's of course not an ordered task list, but to me it makes sense to read this before the 'after deploying' line.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As discussed, starting with 33.0.7
Updating to nextcloud 33.0.7to pr-14.0.0 - Updating to nextcloud 33.0.7@@ -96,3 +96,3 @@order: start-firstlabels:- "coop-cloud.${STACK_NAME}.version=13.2.0+32-fpm"- "coop-cloud.${STACK_NAME}.version=14.0.0+33.0.7-fpm"I think it's not a big problem to leave this in, but it's not needed.
abra recipe releasewill update this label and make sure it matches the release tag.@@ -2,0 +8,4 @@`abra app cmd <app> app run_occ '"app:update --all"'`- Review app (plug-in) compatibility with Nextcloud 33 before upgrading; someapps may need to be updated or temporarily disabled.- Added `check_major_upgrade` (`abra app cmd <app-name> app check_major_upgrade`)This line could be a bit higher in the release notes? It's of course not an ordered task list, but to me it makes sense to read this before the 'after deploying' line.