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

Prepare version v5.0.0 #1336

Merged
merged 4 commits into from
Sep 22, 2020
Merged

Prepare version v5.0.0 #1336

merged 4 commits into from
Sep 22, 2020

Conversation

realm-ci
Copy link
Collaborator

No description provided.

@kraenhansen kraenhansen changed the title Prepare version v4.0.0 Prepare version v5.0.0 Sep 22, 2020

### Breaking Changes

- Added support for reading / writing Realm files using Realm file format v11 (used by realm-js v6.1.1, realm-java v7.0.4, realm-cocoa v5.4.0 and realm-dotnet v5.0.1). When opening a file which is using an older format, you will get prompted to upgrade (and optionally backup) the Realm file. NOTE: Once the file has been upgraded, there is no way to downgrade it again and it can only be used by the SDKs that support Realm file format v11. ([#1331](https://github.com/realm/realm-studio/pull/1331))
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we remove the patch version? Or actually just mention the version where the new fileformat was introduced?

Copy link
Contributor

Choose a reason for hiding this comment

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

Should we add instructions (link?) that describes how to keep the old version of Studio in parallel with the new?
"If you have a need to keep working on both pre v11 and v11 file formats, you can install this new version along an existing version by ..."

Copy link
Member

@kraenhansen kraenhansen Sep 22, 2020

Choose a reason for hiding this comment

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

Should we remove the patch version?

No, I don't think so, since those are the exact versions the new file format got introduced to the respective SDKs. The major versions introduced the v10 file format.

Should we add instructions (link?) that describes how to keep the old version of Studio in parallel with the new?

We don't have that page written up yet. I suggest we patch the changelog (or even better the readme.md) once we have that page ready.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, that's perfect then!

@kraenhansen kraenhansen merged commit a504fda into master Sep 22, 2020
@kraenhansen kraenhansen deleted the ci/prepared-v4.0.0 branch September 22, 2020 09:32
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 19, 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.

None yet

3 participants