-
fix(observability): switch source map upload to glitchtip-cli
Some checks failedRelease / Test backend (push) Successful in 18sCI / Test backend (pull_request) Successful in 18sRelease / Check ui (push) Successful in 47sRelease / Docker / caddy (push) Successful in 55sCI / Check ui (pull_request) Successful in 21sRelease / Docker / backend (push) Failing after 1m13sCI / Docker / backend (pull_request) Failing after 20sRelease / Docker / runner (push) Successful in 1m46sCI / Docker / runner (pull_request) Failing after 1m17sRelease / Docker / ui (push) Failing after 39sCI / Docker / ui (pull_request) Successful in 1m11sCI / Docker / caddy (pull_request) Successful in 7m6sRelease / Upload source maps (push) Failing after 41sRelease / Gitea Release (push) Has been skippedreleased this
2026-03-25 21:10:10 +05:00 | -251 commits to main since this release@sentry/vite-plugin uses sentry-cli which creates release entries but
doesn't upload files to GlitchTip's API correctly. Switch to the native
glitchtip-cli which uses the debug ID inject+upload approach that
GlitchTip actually supports.Downloads