Skip to content

Conversation

@mokagio
Copy link
Contributor

@mokagio mokagio commented Jan 6, 2026

See https://linear.app/a8c/issue/AINFRA-1693


  • I have considered if this change warrants release notes and have added them to the appropriate section in the CHANGELOG.md if necessary.

@mokagio
Copy link
Contributor Author

mokagio commented Jan 6, 2026

Pausing work on this for the moment while I gather input on how to address the failing version consistency check.

Problem: We want the version hardcoded in the source and sent as part as the user agent to be in sync with the library's version as used by the package manager. This was straightforward with CocoaPods because it required hardcoding the version in the podspec. It is no longer as simple with SwiftPM, which delegates version declaration to Git.

There are of course possible solutions we could implement for this, like a CI check that runs only on tags, or updating the script to do something like git fetch && git tag | sort -V | tail -1 to extract the most recent tag and compare it against the hardcoded value.

However, taking a step back I wonder whether we can do away with the library version in the user agent in the first place, thus removing the need for the validation step.

I asked about this internally, ref p1767675546597369-slack-C03DKP1JP.

This has been discussed internally and we decided that the overhead of
keeping the version in sync between code and Git tags was not worth the
value of tracking it in the user agent.

Given we already track the version of the app that logs events via the
library, the library's version can always be deduced.
@mokagio mokagio marked this pull request as ready for review January 7, 2026 01:22
### Internal Changes

- Constrained version to `< 8.49.0` for CocoaPods installations to avoid deprecation warnings till we upgrade Sentry to version 9.x [#310]
- With this version, Tracks only supports distribution via Swift Package Manager [#311]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seemed redundant to track the #310 workaround given it was CocoaPods related.

@mokagio mokagio requested review from iangmaia and twstokes January 7, 2026 01:24
@mokagio mokagio self-assigned this Jan 7, 2026
Copy link

@twstokes twstokes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did a quick scan and didn't spot anything. This should be a low-risk change anyway, so approving. 👍

@twstokes
Copy link

However, taking a step back I wonder whether we can do away with the library version in the user agent in the first place, thus removing the need for the validation step.

Connecting dots as it looks like this was determined in #313.

@mokagio mokagio merged commit 43c2faa into trunk Jan 13, 2026
5 checks passed
@mokagio mokagio deleted the ainfra-1693-remove-cocoapods-distribution-support-from-tracks branch January 13, 2026 05:56
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