Skip to content

Conversation

cahofmeyr
Copy link
Contributor

@cahofmeyr cahofmeyr requested a review from benitav July 8, 2025 15:23
@simolus3
Copy link
Contributor

simolus3 commented Jul 8, 2025

In the Installation section, can we replace the exact dependency with a semver range suggestion?

dependencies: [
        ...
        .package(url: "https://github.com/powersync-ja/powersync-swift", from: "<version>")
],

Now that we're not recommending pinning an exact version anymore, this feels like a better default.

@cahofmeyr
Copy link
Contributor Author

In the Installation section, can we replace the exact dependency with a semver range suggestion?

dependencies: [
        ...
        .package(url: "https://github.com/powersync-ja/powersync-swift", from: "<version>")
],

Now that we're not recommending pinning an exact version anymore, this feels like a better default.

@stevensJourney what are your thoughts?

@stevensJourney
Copy link
Contributor

Thanks for catching and removing the BETA notice 😅 .

For the dependencies. I think we should be able to update the READE example to

dependencies: [
        ...
        .package(url: "https://github.com/powersync-ja/powersync-swift", from: "1.0.0")
],

My understanding is that from: "1.0.0" follows the SemVer range equivalent to ^1.0.0, which means it will install the latest compatible SDK for new users and automatically upgrade as we release new versions. Users are also free to pin the version if they prefer.

I can commit those changes to this branch in order to get this over the line.

@stevensJourney stevensJourney requested a review from simolus3 July 10, 2025 07:00
@simolus3 simolus3 merged commit d25783c into main Jul 10, 2025
3 checks passed
@simolus3 simolus3 deleted the readme-beta branch July 10, 2025 09:53
@cahofmeyr
Copy link
Contributor Author

@simolus3 @stevensJourney I see the README still mentions KMMBridge; should that also be removed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants