Semih Yesilyurt cdf1ced91a fix(observability): tag Sentry environment by host (dev → staging) ...

dev.sase.tr and sase.tr both run NODE_ENV=production (and ship the same
production Vite build), so every Sentry event — api, worker, and browser — was
tagged environment=production, making dev errors indistinguishable from prod.
Resolve the environment from the canonical prod host instead: COOLIFY_FQDN /
BETTER_AUTH_URL on the server (the same signal isCatalogBackfillEnabled uses),
window.location.hostname on the web. So dev now tags as "staging" and stays
filterable. Explicit SENTRY_ENVIRONMENT / VITE_SENTRY_ENVIRONMENT still win.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-09 18:17:06 +03:00

..

drizzle

feat(notifications): operability tier — send_limit + open-pixel + signed-URL exp + retention + sent-flag (audit §9.4)

2026-06-04 17:04:17 +03:00

src

fix(observability): tag Sentry environment by host (dev → staging)

2026-06-09 18:17:06 +03:00

.env.example

feat(api): wire Novu lifecycle email triggers

2026-05-27 01:30:39 +03:00

biome.json

feat(FN-094): add comment line for deployment verification

2026-05-11 02:07:03 +00:00

drizzle.config.ts

feat: sase.tr v2 full application implementation

2026-02-12 02:03:56 +00:00

nest-cli.json

feat: sase.tr v2 full application implementation

2026-02-12 02:03:56 +00:00

package.json

feat(api): source-DB lookup-first for pcat/emex catalog fetches

2026-06-01 00:35:45 +03:00

start.sh

feat(FN-190): move drizzle-kit to production dependencies (+8 more)

2026-05-11 22:03:33 +00:00

tsconfig.json

feat: sase.tr v2 full application implementation

2026-02-12 02:03:56 +00:00

vitest.config.ts

feat(FN-277): add @sase/shared resolve alias to vitest configs for both api and web (+1 more)

2026-05-13 02:07:02 +00:00