Don't lint UID2Prebid podspec during PR tests #84
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
mrmans0n
reviewed
Jan 19, 2026
mrmans0n
approved these changes
Jan 19, 2026
dcaunt
force-pushed
the
dave/podspec-lint
branch
from
87f8b7c to
a601b07
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#83 is failing checks because the pod lint step for UID2Prebid wrapper can only run against the latest production release of its dependency
UID2, which also has changes. There's no way around this using CocoaPods – a release to the dependency has to be made before lint will pass for a new release of the dependent library.Remove the lint step from the PR tests, adding a new PR job that runs if the UID2Prebid podspec itself is modified. The lint was a nice to have, but the library is still compiled during PR checks, and the pod is unlikely to change.