ci: Standardize SDK release failure telemetry

[marandaneto]

💡 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/publish-pub-dev.yml

• Updated .github/workflows/publish.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 }}.

[greptile-apps]

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

[github-actions]

posthog-flutter Compliance Report

Date: 2026-07-02 14:23:09 UTC
Duration: 97010ms

✅ All Tests Passed!

45/45 tests passed

---

Capture Tests

✅ 29/29 tests passed

View Details

Test	Status	Duration
Format Validation.Event Has Required Fields	✅	149ms
Format Validation.Event Has Uuid	✅	123ms
Format Validation.Event Has Lib Properties	✅	120ms
Format Validation.Distinct Id Is String	✅	119ms
Format Validation.Token Is Present	✅	120ms
Format Validation.Custom Properties Preserved	✅	122ms
Format Validation.Event Has Timestamp	✅	121ms
Retry Behavior.Retries On 503	✅	5337ms
Retry Behavior.Does Not Retry On 400	✅	2122ms
Retry Behavior.Does Not Retry On 401	✅	2121ms
Retry Behavior.Respects Retry After Header	✅	8130ms
Retry Behavior.Implements Backoff	✅	15453ms
Retry Behavior.Retries On 500	✅	5231ms
Retry Behavior.Retries On 502	✅	5231ms
Retry Behavior.Retries On 504	✅	5227ms
Retry Behavior.Max Retries Respected	✅	15438ms
Deduplication.Generates Unique Uuids	✅	129ms
Deduplication.Preserves Uuid On Retry	✅	5227ms
Deduplication.Preserves Uuid And Timestamp On Retry	✅	10331ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry	✅	5235ms
Deduplication.No Duplicate Events In Batch	✅	131ms
Deduplication.Different Events Have Different Uuids	✅	120ms
Compression.Sends Gzip When Enabled	✅	120ms
Batch Format.Uses Proper Batch Structure	✅	116ms
Batch Format.Flush With No Events Sends Nothing	✅	110ms
Batch Format.Multiple Events Batched Together	✅	130ms
Error Handling.Does Not Retry On 403	✅	2119ms
Error Handling.Does Not Retry On 413	✅	2120ms
Error Handling.Retries On 408	✅	5230ms

Feature_Flags Tests

✅ 16/16 tests passed

View Details

Test	Status	Duration
Request Payload.Request With Person Properties Device Id	✅	15ms
Request Payload.Flags Request Uses V2 Query Param	✅	13ms
Request Payload.Flags Request Hits Flags Path Not Decide	✅	13ms
Request Payload.Flags Request Omits Authorization Header	✅	12ms
Request Payload.Token In Flags Body Matches Init	✅	12ms
Request Payload.Groups Round Trip	✅	13ms
Request Payload.Groups Default To Empty Object	✅	13ms
Request Payload.Person Properties Distinct Id Auto Populated When Caller Omits It	✅	12ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False	✅	13ms
Request Payload.Disable Geoip Omitted Defaults To False	✅	13ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key	✅	12ms
Request Lifecycle.No Flags Request On Init Alone	✅	6ms
Request Lifecycle.No Flags Request On Normal Capture	✅	116ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests	✅	20ms
Request Lifecycle.Mock Response Value Is Returned To Caller	✅	13ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event	✅	120ms

[greptile-apps]

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