Skip to content

Conversation

@backportbot-nextcloud
Copy link

@backportbot-nextcloud backportbot-nextcloud bot commented Feb 17, 2023

  • ⚠️ This backport had conflicts and is incomplete

backport of #323

@backportbot-nextcloud backportbot-nextcloud bot added the bug Something isn't working label Feb 17, 2023
@backportbot-nextcloud backportbot-nextcloud bot added this to the 1.1.1 milestone Feb 17, 2023
@st3iny st3iny added the 3. to review Waiting for reviews label Feb 17, 2023
Fixes #233

Signed-off-by: Zev Lee <[email protected]>
Signed-off-by: Richard Steinmetz <[email protected]>
@st3iny st3iny force-pushed the backport/323/stable1.1 branch from 63b116c to f36b0dd Compare February 17, 2023 14:58
@st3iny
Copy link
Member

st3iny commented Feb 17, 2023

@ChristophWurst Is backporting a migration fine or shall we wait until the next minor release?

@ChristophWurst
Copy link
Member

As long as it doesn't depend on a schema that does not exist for the older version it is fine

And Nextcloud will also only run that migration once if the name is identical 👍

@st3iny st3iny merged commit 6bc75e9 into stable1.1 Feb 23, 2023
@st3iny st3iny deleted the backport/323/stable1.1 branch February 23, 2023 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants