Move to automated dependabot merging

[skjnldsv]

Currently this auto merge patch releases.

While I think it's fine to auto-merge minor on other apps.
I'd be more cautious on server

cc @nextcloud/javascript

[georgehrke]

The dependabot.yml is missing plenty of our current config:

[skjnldsv]

Done @georgehrke !
I think it doesn't make sense to keep upgrading npm in /build for stablexx versions.
Testui integration has been removed from master now and is outdated.

[skjnldsv]

Hum, actually, do we want to keep upgrading /build/integration for stablexx branches?
I would only upgrade main npm to be honest

[skjnldsv]

Damnit

EDIT: dependabot/dependabot-core#2159 (comment)

[faily-bot]

🤖 beep boop beep 🤖

Here are the logs for the failed build:

Status of 32756: failure

acceptance-app-files-sharing

• tests/acceptance/features/app-files-sharing.feature:338

Show full log

 Scenario: sharee can revoke create permission from reshare after the sharer disabled it # /drone/src/tests/acceptance/features/app-files-sharing.feature:338
Given I act as John # ActorContext::iActAs()
And I am logged in as the admin # LoginPageContext::iAmLoggedInAsTheAdmin()
And I act as Jane # ActorContext::iActAs()
And I am logged in # LoginPageContext::iAmLoggedIn()
And I act as Jim # ActorContext::iActAs()
And I am logged in as "user1" # LoginPageContext::iAmLoggedInAs()
And I act as John # ActorContext::iActAs()
And I create a new folder named "Shared folder" # FileListContext::iCreateANewFolderNamed()
And I see that the file list contains a file named "Shared folder" # FileListContext::iSeeThatTheFileListContainsAFileNamed()
And I share "Shared folder" with "user0" # FilesAppSharingContext::iShareWith()
And I see that the file is shared with "user0" # FilesAppSharingContext::iSeeThatTheFileIsSharedWith()
And I act as Jane # ActorContext::iActAs()
And I open the Files app # FilesAppContext::iOpenTheFilesApp()
And I share "Shared folder" with "user1" # FilesAppSharingContext::iShareWith()
And I see that the file is shared with "user1" # FilesAppSharingContext::iSeeThatTheFileIsSharedWith()
And I act as John # ActorContext::iActAs()
And I set the share with "user0" as not creatable # FilesAppSharingContext::iSetTheShareWithAsNotCreatable()
And I see that "user0" can not create in the share # FilesAppSharingContext::iSeeThatCanNotCreateInTheShare()
And I act as Jim # ActorContext::iActAs()
And I open the Files app # FilesAppContext::iOpenTheFilesApp()
And I enter in the folder named "Shared folder" # FileListContext::iEnterInTheFolderNamed()
And I create a new folder named "Subfolder" # FileListContext::iCreateANewFolderNamed()
And I see that the file list contains a file named "Subfolder" # FileListContext::iSeeThatTheFileListContainsAFileNamed()
When I act as Jane # ActorContext::iActAs()
And I open the Files app # FilesAppContext::iOpenTheFilesApp()
And I open the details view for "Shared folder" # FileListContext::iOpenTheDetailsViewFor()
And I see that the details view is open # FilesAppContext::iSeeThatTheDetailsViewIsOpen()
And I open the "Sharing" tab in the details view # FilesAppContext::iOpenTheTabInTheDetailsView()
And I see that the "Sharing" tab in the details view is eventually loaded # FilesAppContext::iSeeThatTheTabInTheDetailsViewIsEventuallyLoaded()
And I set the share with "user1" as not creatable # FilesAppSharingContext::iSetTheShareWithAsNotCreatable()
Then I see that "user1" can not create in the share # FilesAppSharingContext::iSeeThatCanNotCreateInTheShare()
And I see that "user1" can not be allowed to create in the share # FilesAppSharingContext::iSeeThatCanNotBeAllowedToCreateInTheShare()
And I act as Jim # ActorContext::iActAs()
And I open the Files app # FilesAppContext::iOpenTheFilesApp()
And I enter in the folder named "Shared folder" # FileListContext::iEnterInTheFolderNamed()
And I see that it is not possible to create new files # FileListContext::iSeeThatItIsNotPossibleToCreateNewFiles()
Failed asserting that true is false.

[georgehrke]

Looks good to me, but i can't judge the part regarding the integration test suite.

[juliusknorr]

Hum, actually, do we want to keep upgrading /build/integration for stablexx branches?

Yeah just security updates i'd say for those.

We can just adjust the string of the branches when backporting the dependabot config to the stable branches.

[skjnldsv]

Yeah just security updates i'd say for those.

We can just adjust the string of the branches when backporting the dependabot config to the stable branches.

No, because dependabot doesn't check other branches than master
So we need to adjust master only.
Regarding security updates, I think they follow an independent release process. So it doesn't matter rather we have a dependabot config or not as long as it's enabled in https://github.com/nextcloud/server/network/alerts & https://github.com/nextcloud/server/settings/security_analysis

[skjnldsv]

https://github.com/nextcloud/server/network/updates