ci: Dont upload artifacts for non-release related runs

[kamilogorek]

Saves us time and resources.

[github-actions]

size-limit report

Path	Base Size (72aed62)	Current Size	Change
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	19.49 KB	19.49 KB	+0.01% 🔺
@sentry/browser - ES5 CDN Bundle (minified)	62.17 KB	62.17 KB	0%
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	18.11 KB	18.11 KB	-0.01% 🔽
@sentry/browser - ES6 CDN Bundle (minified)	55.5 KB	55.5 KB	0%
@sentry/browser - Webpack (gzipped + minified)	22.41 KB	22.41 KB	0%
@sentry/browser - Webpack (minified)	76.82 KB	76.82 KB	0%
@sentry/react - Webpack (gzipped + minified)	22.45 KB	22.45 KB	0%
@sentry/nextjs Client - Webpack (gzipped + minified)	46.62 KB	46.62 KB	0%
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	25.36 KB	25.36 KB	0%
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	23.72 KB	23.72 KB	+0.01% 🔺

[Lms24]

Seems like a good idea and it will for sure save some time. I have a question though: when this PR is merged, is there still a way of checking that the artifacts archive is created correctly? For example, I when I was doing the build dir change (#4688) it was helpful for me to download and inspect the artifacts file. Found out that I was initially uploading more JS files than just the bundles.

[kamilogorek]

is there still a way of checking that the artifacts archive is created correctly?

You can name your branch release/testing-artifacts or anything with release/ prefix and it will run the workflow just as you'd be running it when publishing new version (without actually triggering new version build).

[Lms24]

I see. Given that we probably won't need to check artifacts generation often, I think that's a good change.

[lobsterkatie]

Good change!

[lobsterkatie]

You can name your branch release/testing-artifacts or anything with release/ prefix and it will run the workflow just as you'd be running it when publishing new version (without actually triggering new version build).

You can also, in your branch, change this condition to include the branch's name and then just drop the commit which does so before the PR is finalized. (I find that easier than keeping track of branches named something other than what I'd expect.)

[Lms24]

That's a good idea as well, thanks 👍