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: update bigint in podspec #370

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

metalurgical
Copy link

@metalurgical metalurgical commented Apr 22, 2024

BigInt 5.3 (as defined in the spm package) is not backwards compatible beyond 5.2 (as defined in the cocoapods package).

There are missing extensions.

@DarthMike
Copy link
Member

Hi @metalurgical we already updated to 5.3, even if not backwards compatible. Better to keep the versions aligned (SPM vs Cocoapods)

@metalurgical
Copy link
Author

Hi @DarthMike.

Perhaps the explanation was unclear.

The latest BigInt release on Cocoapods is 5.2. On Swift Package Manager it is 5.3.

BigInt 5.2 is compatible with BigInt 5.3, except for a couple extensions added in 5.3.

However versions before 5.2 are very difficult to be compatible with 5.3 so the cocoapods version needs to be updated.

Does this explain it better?

@DarthMike
Copy link
Member

@metalurgical Thanks for clarification.
I see what you mean, but if we update the podspec I think we should bump to be using minimum 5.3 as we do for SPM. Even if we're forcing an update of the library it's going to be better longer term.

Are there any other common libraries that will not be compatible if it's bumped to 5.3?

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.

2 participants