Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Create a release X for projects A and B (monorepo, thus A and B share the same commit hash)
2. Deploy project A to environment E
3. Observe that a deployment for project B in environment E was also created

Expected Result

A could be a service (that runs in all environments) and B a cronjob (that only runs in prod). Both A and B come from the same monorepo and when A is deployed to staging, a staging deployment for B is also created.

Instead, when deploying A to staging, the deploy should be only created for A and has nothing to do with B. They share the same release, but not deploys.

Actual Result

I run the manual CI job "deploy A to staging" and I get (both mail and in Slack):

and the Sentry dashboard shows the same.

Product Area

Releases

Link

No response

DSN

No response

Version

No response