fix: dependencies sentry

[TartanLeGrand]

For fix the dependencies if we are in monorepo.

This version of Sentry Capacitor is incompatible with the following installed packages:
@sentry/tracing version ^7.60.1
@sentry/vue version ^7.60.1
Please install the mentioned packages exactly with version 7.54.0 and with the argument --update-sentry-capacitor
yarn add --exact @sentry/[email protected] @sentry/[email protected]  --update-sentry-capacitor

[lucas-zimerman]

I am aware that it may be annoying, but we planned to only use fixed versions, so instead, I would recommend changing those versions to "7.60.1" instead of "^7.56.0"

This may be mitigated in the future if we do more frequent releases bumping Sentry JavaScript

[TartanLeGrand]

But you don't follow the sentry official version when they are published

[maxnowack]

@lucas-zimerman what's the reason for this?

[lucas-zimerman]

The main reason is we want to make sure that the release of capacitor SDK works with the given Sentry Siblings releases.

Are you not able to install Sentry Capacitor version 0.12.2 with Sentry React 7.56.0?

[TartanLeGrand]

Okay, but in the semantic versioning the second digit is the minor version, if you don't need the features of the 7.60.x you can stay in 7.56.0 in your minimal dependencies and you still stay compatible with the nexts minor versions.

And we have an monorepo with capacitor and vuejs but we keep our packages up to date. If You need you can go to 7.60.1 with an ^ for keep compatibility with other minors.

[github-actions]

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[Jorgagu]

@lucas-zimerman any update ? 🤔

[krystofwoldrich]

We have discussed this with the team and decided to keep the dependencies locked for now.

The stability of the SDK is a priority for us and locking the exact version of the JS SDK helps with it. We follow semver with our public interfaces, but we also use private APIs in our SDKs that might not be compatible between versions.

This doesn't apply only to JS but also to sentry-java and sentry-cocoa dependencies.

Thank you for bringing this to our attention we will be releasing new versions more frequently to keep up closer to the latest sentry-javascript versions.

[TartanLeGrand]

How we can have 2 diff versions in a mono repo ?

[maxnowack]

@krystofwoldrich thanks for taking care of this. This is a good explanation of why version pinning should be maintained.

What would make updating sentry packages easier on our end would be if all packages followed the same versioning scheme. For example, all packages in the sentry-javascript monorepo have the same version number. sentry-capacitor is also used exclusively in the javascript context, but has a different versioning. This makes updating the packages a bit difficult at the moment, since you can't just bump the sentry-javascript version without first checking which is the corresponding sentry-capacitor version.
Maybe it would be an idea to include sentry-capacitor in the monorepo of sentry-javascript (if that makes sense).