Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Sentry Integration: Dynamic release tagging

Aperta
  • Qualcosa non va?
#1,242 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@vprashrex ci sta già lavorando.

Dal 10/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement parent

Is your feature request related to a problem?
Sentry currently reports a static release (0.5.0) for both kaapi-production and kaapi-staging. This prevents tracking which commit or deploy introduced issues, limiting regression detection.

Describe the solution you'd like

  • Tag every deploy with kaapi-backend@<tag or main>+<git sha 12> and register it in Sentry.
  • Split CI/CD changes into two sub-issues:
    • #1240 Production: tag push → ECS (create-release.yml)
    • #1241 Staging: main merge → EC2 (deploy-staging.yml)
  • Implement shared changes in release-id code (resolve_sentry_release, RELEASE_TAG setting, Dockerfile build arg) with the first sub-issue.
Original issue

Describe the current behavior
Sentry reports a static release (0.5.0) for both kaapi-production and kaapi-staging, with no commits or deploys attached. Neither environment can show which commit or deploy introduced an issue.

Describe the enhancement you'd like
Tag every deploy with kaapi-backend@<tag or main>+<git sha 12> and register it in Sentry with its commits. Production and staging deploy through different workflows, so the CI/CD changes are split into two sub-issues:

  • #1240 Production: tag push → ECS (create-release.yml)
  • #1241 Staging: main merge → EC2 (deploy-staging.yml)

The release-id code change (resolve_sentry_release, RELEASE_TAG setting, Dockerfile build arg) is shared; land it with whichever sub-issue goes first.

Why is this enhancement needed?
Regression detection, suspect commits and "resolved in next release" in Sentry all depend on a release id that changes per deploy.

Additional context
Draft implementation and runbook: #1234.

Lingua principale
Python
Stelle
18
Fork
11
Merge medio
3g 11h
PR unite (30g)
8

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ProjectTech4DevAI/kaapi-backend

Tutte le issue di ProjectTech4DevAI/kaapi-backend

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.