You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this generally doesn’t cause issues, it’s worth mentioning that there were some tagging problems in grpc-swift version 1.24.0, which can occasionally lead to package resolution issues.
To address this, I was wondering if we could unify the versioning approach. Some possible solutions that would also prevent the previously mentioned issue could include:
Defining exact: 1.0.0 across all Package.swift files.
Defining from: 1.24.1 across all Package.swift files.
Defining exact: 1.24.2 (the latest) across all Package.swift files.
If this sounds good, I’d be happy to open a PR and test the changes.
Let me know your thoughts!
The text was updated successfully, but these errors were encountered:
Hi there! Since the merge of this pull request, I've noticed a discrepancy in the versioning of
grpc-swift
:Package.swift
, it usesexact: 1.0.0
.[email protected]
and[email protected]
, it usesfrom: 1.0.0
.While this generally doesn’t cause issues, it’s worth mentioning that there were some tagging problems in grpc-swift version 1.24.0, which can occasionally lead to package resolution issues.
To address this, I was wondering if we could unify the versioning approach. Some possible solutions that would also prevent the previously mentioned issue could include:
exact: 1.0.0
across allPackage.swift
files.from: 1.24.1
across allPackage.swift
files.exact: 1.24.2
(the latest) across allPackage.swift
files.If this sounds good, I’d be happy to open a PR and test the changes.
Let me know your thoughts!
The text was updated successfully, but these errors were encountered: