mirror of
https://github.com/MarijnDoeve/TijdVoorDeTest.git
synced 2026-07-04 22:50:15 +02:00
b1f84d441f
The Sentry action receives the v-stripped version (e.g. 0.1.1) but the app's SENTRY_RELEASE was set to IMAGE_TAG (e.g. v0.1.1). This caused Sentry to auto-create a second release from incoming events, labelling it (non-semver) instead of associating events with the properly created release. Pass SENTRY_RELEASE as a separate query param through the Portainer webhook (using the already-computed sentry_version output) and reference that in compose.prod.yaml instead of IMAGE_TAG.