Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump core to version 13.23.1 #1545

Merged
merged 13 commits into from
Oct 19, 2023
Merged

Bump core to version 13.23.1 #1545

merged 13 commits into from
Oct 19, 2023

Conversation

clementetb
Copy link
Contributor

Bumps core to version 13.23.0.

Core has removed realm_user_get_auth_provider, in reaction to this we have annotated User.provider as deprecated and now returns the first element auth provider at User.identities.

@clementetb clementetb self-assigned this Oct 12, 2023
Copy link
Contributor

@cmelchior cmelchior left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably target main with this. But otherwise 👍 if CI is green.

@clementetb clementetb changed the base branch from releases to main October 13, 2023 11:20
@cmelchior
Copy link
Contributor

We should also fix #1546 as part of this

@clementetb
Copy link
Contributor Author

closes #1546

@@ -391,7 +391,7 @@ class AppTests {
Realm.open(syncConfig).close()

// Create a configuration pointing to the metadata Realm for that app
val lastSetSchemaVersion = 6L
val lastSetSchemaVersion = 7L
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. I don't really know the full consequence of this, but from this comment it seems that we should at least warn about not being able to downgrade 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are opening the metadata directly instead of opening a higher schema version with an app to trigger a schema downgrade.

I am going to create a ticket to validate what is the expected behavior when downgrading an App metadata schema.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh sorry, forgot the link to the comment I was referring to: #1528 (comment)

@cmelchior cmelchior changed the title Bump core to version 13.23.0 Bump core to version 13.23.1 Oct 19, 2023
Copy link
Contributor

@cmelchior cmelchior left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small suggestion for the changelog, otherwise 👍

CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Christian Melchior <[email protected]>
@clementetb clementetb merged commit 93a05a1 into main Oct 19, 2023
1 of 2 checks passed
@clementetb clementetb deleted the ct/bump-core-13.23.0 branch October 19, 2023 09:31
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants