You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Breaking Change — Echo v5: PR #1183 is marked feat! (breaking change). The Echo integration (sentry-go/echo) now requires github.com/labstack/echo/v5 and Go 1.25. Echo v4 support has been dropped. The skill currently documents sentry-go/echo without version distinction, and the detection step (Phase 1) looks for labstack/echo without specifying v4 vs v5. Users on Echo v4 following the skill could inadvertently upgrade or encounter breakage. The skill needs to:
Update the detection pattern to distinguish v4 vs v5
Note the minimum Go version requirement (1.25) for Echo users
Clarify that sentry-go/echo now requires Echo v5
New OTLP Integration: PR #1229 introduces sentryotlp.NewTraceExporter — a new package (github.com/getsentry/sentry-go/otlp) for sending OTLP traces directly to Sentry's OTLP endpoint without using the OTel bridge. This is distinct from the existing sentry-go/otel bridge. The skill's tracing.md currently covers the OTel bridge but not the native OTLP exporter. A new subsection is needed explaining when to use OTLP vs. the OTel bridge.
Why This Needs Manual Review
The Echo v5 breaking change requires migration guidance (users still on Echo v4 need to know their options)
The OTLP integration introduces a new Go package path (sentry-go/otlp) and new API (sentryotlp.NewTraceExporter, sentryotel.NewOtelIntegration) that needs a complete code example
The two changes together require coordinated updates to SKILL.md (detection, install, middleware table) and references/tracing.md (new OTLP section)
The minimum Go version bump (1.25 for Echo users) may affect the skill's prerequisites section
cc
@getsentry/team-web-sdk-backendSDK Changes Detected
The following PRs were merged to
getsentry/sentry-goin the last 7 days that may affect thesentry-go-sdkskill:Potential Skill Gaps
Breaking Change — Echo v5: PR
#1183is markedfeat!(breaking change). The Echo integration (sentry-go/echo) now requiresgithub.com/labstack/echo/v5and Go 1.25. Echo v4 support has been dropped. The skill currently documentssentry-go/echowithout version distinction, and the detection step (Phase 1) looks forlabstack/echowithout specifying v4 vs v5. Users on Echo v4 following the skill could inadvertently upgrade or encounter breakage. The skill needs to:sentry-go/echonow requires Echo v5New OTLP Integration: PR
#1229introducessentryotlp.NewTraceExporter— a new package (github.com/getsentry/sentry-go/otlp) for sending OTLP traces directly to Sentry's OTLP endpoint without using the OTel bridge. This is distinct from the existingsentry-go/otelbridge. The skill's tracing.md currently covers the OTel bridge but not the native OTLP exporter. A new subsection is needed explaining when to use OTLP vs. the OTel bridge.Why This Needs Manual Review
sentry-go/otlp) and new API (sentryotlp.NewTraceExporter,sentryotel.NewOtelIntegration) that needs a complete code exampleSKILL.md(detection, install, middleware table) andreferences/tracing.md(new OTLP section)Skill Files to Review
skills/sentry-go-sdk/SKILL.md(Phase 1 detection, install step, framework middleware table)skills/sentry-go-sdk/references/tracing.md(Echo middleware section, new OTLP section)Priority
HIGH for Echo v5 (breaking change that could mislead users on v4); MEDIUM for OTLP integration (new additive feature)
Note
🔒 Integrity filter blocked 21 items
The following items were blocked because they don't meet the GitHub integrity level.
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: