Skip to content

ci: Standardize SDK release failure telemetry#159

Open
marandaneto wants to merge 1 commit into
mainfrom
sdk-release-failure-telemetry
Open

ci: Standardize SDK release failure telemetry#159
marandaneto wants to merge 1 commit into
mainfrom
sdk-release-failure-telemetry

Conversation

@marandaneto

@marandaneto marandaneto commented Jul 2, 2026

Copy link
Copy Markdown
Member

💡 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?

  • Parsed modified workflow YAML successfully.
  • Ran git diff --check.
  • Verified modified PostHog release failure events use posthog-sdk-github-release-workflow-failure and include the expected metadata.

📝 Checklist

  • I reviewed the submitted code.
  • I added tests to verify the changes.
  • I updated the docs if needed.
  • No breaking change or entry added to the changelog.

If releasing new changes

  • Ran changeset generation for a release changeset file

🤖 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.yml

  • Use the shared posthog-sdk-github-release-workflow-failure event for SDK release failure telemetry.\n- Use latest pinned action versions for PostHog/posthog-github-action and PostHog/.github/.github/actions/slack-thread-reply.n- Include consistent metadata: repository, sdk, jobName, packageName, packageVersion, actionUrl, alertText, and alertContext.\n- Keep actionUrl pointing at https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}.

@marandaneto marandaneto self-assigned this Jul 2, 2026
@greptile-apps

greptile-apps Bot commented Jul 2, 2026

Copy link
Copy Markdown

Reviews (1): Last reviewed commit: "ci: standardize SDK release failure tele..." | Re-trigger Greptile

Comment thread .github/workflows/release.yml
Comment thread .github/workflows/release.yml Outdated
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

posthog-elixir Compliance Report

Date: 2026-07-02 13:52:18 UTC
Duration: 117589ms

✅ All Tests Passed!

46/46 tests passed


Capture Tests

29/29 tests passed

View Details
Test Status Duration
Format Validation.Event Has Required Fields 610ms
Format Validation.Event Has Uuid 609ms
Format Validation.Event Has Lib Properties 610ms
Format Validation.Distinct Id Is String 609ms
Format Validation.Token Is Present 610ms
Format Validation.Custom Properties Preserved 608ms
Format Validation.Event Has Timestamp 609ms
Retry Behavior.Retries On 503 5615ms
Retry Behavior.Does Not Retry On 400 2612ms
Retry Behavior.Does Not Retry On 401 2612ms
Retry Behavior.Respects Retry After Header 5615ms
Retry Behavior.Implements Backoff 15625ms
Retry Behavior.Retries On 500 5615ms
Retry Behavior.Retries On 502 5615ms
Retry Behavior.Retries On 504 5614ms
Retry Behavior.Max Retries Respected 15611ms
Deduplication.Generates Unique Uuids 620ms
Deduplication.Preserves Uuid On Retry 5615ms
Deduplication.Preserves Uuid And Timestamp On Retry 10620ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry 5617ms
Deduplication.No Duplicate Events In Batch 613ms
Deduplication.Different Events Have Different Uuids 612ms
Compression.Sends Gzip When Enabled 609ms
Batch Format.Uses Proper Batch Structure 610ms
Batch Format.Flush With No Events Sends Nothing 606ms
Batch Format.Multiple Events Batched Together 614ms
Error Handling.Does Not Retry On 403 2612ms
Error Handling.Does Not Retry On 413 2611ms
Error Handling.Retries On 408 5615ms

Feature_Flags Tests

17/17 tests passed

View Details
Test Status Duration
Request Payload.Request With Person Properties Device Id 610ms
Request Payload.Flags Request Uses V2 Query Param 608ms
Request Payload.Flags Request Hits Flags Path Not Decide 610ms
Request Payload.Flags Request Omits Authorization Header 608ms
Request Payload.Token In Flags Body Matches Init 609ms
Request Payload.Groups Round Trip 610ms
Request Payload.Groups Default To Empty Object 609ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False 609ms
Request Payload.Disable Geoip Omitted Defaults To False 608ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key 609ms
Request Lifecycle.No Flags Request On Init Alone 4ms
Request Lifecycle.No Flags Request On Normal Capture 608ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests 1215ms
Request Lifecycle.Mock Response Value Is Returned To Caller 609ms
Retry Behavior.Retries Flags On 502 911ms
Retry Behavior.Retries Flags On 504 912ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event 1212ms

@marandaneto marandaneto force-pushed the sdk-release-failure-telemetry branch from fb0b939 to 479f145 Compare July 2, 2026 13:25
@marandaneto marandaneto force-pushed the sdk-release-failure-telemetry branch from 479f145 to 60c1895 Compare July 2, 2026 13:49
@marandaneto marandaneto marked this pull request as ready for review July 2, 2026 13:57
@marandaneto marandaneto requested a review from a team as a code owner July 2, 2026 13:57
@greptile-apps

greptile-apps Bot commented Jul 2, 2026

Copy link
Copy Markdown

Reviews (2): Last reviewed commit: "ci: standardize SDK release failure tele..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant