Detected package version outside of dependency constraint

[jamescrosswell]

DESCRIBE YOUR PR

Added docs on troubleshooting "Detected package version outside of dependency constraint" errors.

Resolves getsentry/sentry-dotnet#4095 (see comment)

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• None: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• cc: @Flash0ver

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sentry-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 20, 2025 8:20am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
changelog	⬜️ Ignored (Inspect)	Visit Preview		May 20, 2025 8:20am
develop-docs	⬜️ Ignored (Inspect)	Visit Preview		May 20, 2025 8:20am

[codecov]

Bundle Report

Changes will decrease total bundle size by 15 bytes (-0.0%) ⬇️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
sentry-docs-server-cjs	11.2MB	-9 bytes (-0.0%) ⬇️
sentry-docs-client-array-push	9.51MB	-6 bytes (-0.0%) ⬇️

Affected Assets, Files, and Routes:

view changes for bundle: sentry-docs-server-cjs

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
1729.js	-3 bytes	1.75MB	-0.0%
../instrumentation.js	-3 bytes	1.08MB	-0.0%
9523.js	-3 bytes	1.05MB	-0.0%

view changes for bundle: sentry-docs-client-array-push

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
static/chunks/pages/_app-*.js	-3 bytes	868.7kB	-0.0%
static/chunks/8165-*.js	-3 bytes	410.1kB	-0.0%
server/middleware-*.js	-5.55kB	1.0kB	-84.74%
server/middleware-*.js	5.55kB	6.55kB	555.3% ⚠️
static/vHnnbHEuWfnvd-*.js (New)	578 bytes	578 bytes	100.0% 🚀
static/vHnnbHEuWfnvd-*.js (New)	77 bytes	77 bytes	100.0% 🚀
static/-*.js (Deleted)	-578 bytes	0 bytes	-100.0% 🗑️
static/-*.js (Deleted)	-77 bytes	0 bytes	-100.0% 🗑️

[bruno-garcia]

should we just bump the version we depend on to match Essentials? everyone uses that. basically can't build an app without it.

[jamescrosswell]

should we just bump the version we depend on to match Essentials? everyone uses that. basically can't build an app without it.

We could. There's a risk we create another diamond dependency somewhere else, although if Essentials is really widespread then people would already be bumping into such a problem if it already exists. And although it's the opposite of what we do with most of our integrations, the MAUI community is kind of obliged to live on the bleeding edge (since changes get shipped by Apple and Google, not just Microsoft).

So, sure... yeah, we could do that.

Note that Essentials is a moving target though. Since this issue was reported with version 9.0.50 of that package, another 4 releases and 5 pre-releases of that package have been made.

[riccardominato]

should we just bump the version we depend on to match Essentials? everyone uses that. basically can't build an app without it.

I second this approach. Essentials is always present in MAUI templates and I've never seen a project excluding it.
IMO it's way preferable than adding noise being forced to edit the .csproj file.

[jamescrosswell]

I second this approach. Essentials is always present in MAUI templates and I've never seen a project excluding it.

I'm OK with that. Which version of Maui Essentials do we try to match though? At the moment, we're essentially matching the version of Maui Essentials that was released when MAUI 9 was released. Here are all of the 9.x that have been released (and there are some 10.x releases starting now as well):

@bruno-garcia we could set up an automated dependency check on GitHub and try to bump this automatically so that we're always matching the latest version of Essentials. Other than doing what we're doing (picking the oldest version) that seems like the only other non-arbitrary version we could pick.