Fixed dependencies rules and also bumped to OTel-Core 2.2.0 #958
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ArielDemarco
requested review from
bryce-b,
nachoBonafonte and
vvydier
as code owners
vvydier
approved these changes
Oct 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
The goal of this PR is to fix the issue that occurred when releasing version
2.2.0of the various pods to CocoaPods. Specifically, some exporters pods:OpenTelemetry-Swift-Protocol-Exporter-CommonandOpenTelemetry-Swift-Protocol-Exporter-Http.Details
The issue was that the dependency resolution rule (
~> major.minor.patch) didn't allow picking up the next version, which already included some of the implemented code changes.I updated the version rules so they can pick up not only patch versions but also minor ones. Additionally, I bumped the dependency to use version
2.2.0.