Someone with power will have to override for merge during freeze.

The cypress failures appear completely unrelated:

 1) Files: Move or copy files
       Can copy a file to new folder:
     AssertionError: Timed out retrying after 4000ms: Expected to find element: `[data-cy-files-list-row-name="original.txt"]`, but never found it.
      at Context.eval (webpack://nextcloud/./cypress/e2e/files/files_copy-move.cy.ts:55:38)

  2) Files: Move or copy files
       Can move a file to its parent folder:
     AssertionError: Timed out retrying after 4000ms: Expected to find content: 'No files in here' within the element: <main#app-content-vue.app-content.no-snapper> but never did.
      at Context.eval (webpack://nextcloud/./cypress/e2e/files/files_copy-move.cy.ts:116:52)

Not considered critical → 28.0.3

Not considered critical → 28.0.3

Agreed, I guess, but just a soft nudge and I'll leave it at that 😄 It's a support / user experience matter (with the setup checks) and bug triage time waster. In the docker repo alone, the addition of this check in v28 generated over 75 upvotes and 48 comments just in the past 30 days: nextcloud/docker#2118

Not considered critical → 28.0.3

Agreed, I guess, but just a soft nudge and I'll leave it at that 😄 It's a support / user experience matter (with the setup checks) and bug triage time waster. In the docker repo alone, the addition of this check in v28 generated over 75 upvotes and 48 comments just in the past 30 days: nextcloud/docker#2118

People can ignore the warning or install the module, there is nothing critical about this.

We had already crowded RCs on 28 after the first one, with just important considered PRs. At this stage of a release, the less the better. More, even if they look innocent, just muddy the water while the testing time is very short.