Sentry Integration: Dynamic release tagging
维护者通常 1 天内回复
@vprashrex 已经在做这个了。
开始于 2026年10月10日。
评估
这个 Issue 还没有评估数据。
描述
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:
mainmerge → EC2 (deploy-staging.yml)
- #1240 Production: tag push → ECS (
- Implement shared changes in release-id code (
resolve_sentry_release,RELEASE_TAGsetting, 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:
mainmerge → 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.
- 主要语言
- Python
- 星标
- 18
- 派生
- 11
- 平均合并
- 3 天 11 小时
- 30 天内合并 PR
- 8
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ProjectTech4DevAI/kaapi-backend 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
ProjectTech4DevAI/kaapi-backend#889 ·
维护者通常 1 天内回复
-
Evaluation: Improve guardrails awareness可能已有人在做 @AkhileshNegi 于 15 天前认领。 未关闭enhancement
难度 5/5 一周以上 新手友好度 15/100
ProjectTech4DevAI/kaapi-backend#1246 ·
维护者通常 1 天内回复
-
Logging: Reduce INFO log noise可能已有人在做 @vprashrex 于 3 天前认领。 未关闭maintenance
ProjectTech4DevAI/kaapi-backend#1243 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Sentry Integration: Track staging commits可能已有人在做 @vprashrex 于 3 天前认领。 未关闭enhancement
ProjectTech4DevAI/kaapi-backend#1241 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Sentry release tracking for production (git sha + deploy markers)可能已有人在做 @vprashrex 于 3 天前认领。 未关闭enhancement
ProjectTech4DevAI/kaapi-backend#1240 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 ProjectTech4DevAI/kaapi-backend 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 78/100
uniswap-python/uniswap-python#487 ·
-
[Bug]: agent_final_response still returns the abandoned branch's answer after navigate moves HEAD back可能已有人在做 @enyst 今天认领。 未关闭bug priority:low ready-for-dev
难度 2/5 1-3 小时 新手友好度 72/100
OpenHands/software-agent-sdk#5822 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
-
area: server enhancement good first issue
难度 2/5 1-3 小时 新手友好度 82/100
scs0209/laya-guard#52 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 2 天内回复