ci: Standardize SDK release failure telemetry#159
Open
marandaneto wants to merge 1 commit into
Open
Conversation
|
Reviews (1): Last reviewed commit: "ci: standardize SDK release failure tele..." | Re-trigger Greptile |
Contributor
posthog-elixir Compliance ReportDate: 2026-07-02 13:52:18 UTC ✅ All Tests Passed!46/46 tests passed Capture Tests✅ 29/29 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
fb0b939 to
479f145
Compare
479f145 to
60c1895
Compare
|
Reviews (2): Last reviewed commit: "ci: standardize SDK release failure tele..." | Re-trigger Greptile |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💡 Motivation and Context
Release workflow failures are currently reported with repo-specific PostHog event names or have gaps in pre-publish failure coverage. That would require separate Hog function handling per SDK and makes cross-SDK release failure monitoring harder.
💚 How did you test it?
git diff --check.posthog-sdk-github-release-workflow-failureand include the expected metadata.📝 Checklist
If releasing new changes
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
This PR was prepared with Pi after a human requested consistent SDK release failure telemetry. The change is limited to GitHub Actions release workflow telemetry; no runtime SDK code is changed.
Changes:
Updated
.github/workflows/release.ymlUse the shared
posthog-sdk-github-release-workflow-failureevent for SDK release failure telemetry.\n- Use latest pinned action versions forPostHog/posthog-github-actionandPostHog/.github/.github/actions/slack-thread-reply.n- Include consistent metadata:repository,sdk,jobName,packageName,packageVersion,actionUrl,alertText, andalertContext.\n- KeepactionUrlpointing athttps://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}.