[ablaszkiewicz]

Problem

• The release step from feat(error-tracking): pass the release id into the django image #104420 lives in two copies that nobody else can reuse: one for the CD image build and a mirror for the Depot outage build.
• The same step now ships as a public, versioned action, PostHog/resolve-release v1.0.0.
• feat(error-tracking): pass the release id into the django image #104420 is merged, so this PR targets master directly.

Changes

• Both image builds call PostHog/resolve-release, pinned to the v1.0.0 commit SHA. The image still gets POSTHOG_RELEASE_ID, so deploys see no difference.
• The in-repo composite action and its Depot mirror are deleted.
• Both steps pass project-id: '2' and release-name: posthog explicitly. The deleted action defaulted to them, and the Dockerfile sourcemap stage looks up the release by the same name and version.
• A download, checksum, or API error now fails the step instead of only warning. The step-level continue-on-error still keeps the build going with an empty id.
• A missing secret still gives an empty id and a warning, and the step passes.
• The action pins CLI 0.18.3 with a checksum-verified installer. The Dockerfile keeps its own 0.18.2 pin, because both sides find the release by name and version.

Note

Not verified: whether Depot CI sets GITHUB_ACTION_PATH for a remote composite action. The action needs it to find its script. If it is unset, the outage image ships without the id, which continue-on-error covers. Depot CI already runs a remote action here (PostHog/posthog-github-action in .depot/workflows/ci-backend.yml), but that one is a Node action.

How did you test this code?

• The action's own test run covers the empty-key path on Linux and macOS runners.
• PostHog/resolve-release@v1 ran end to end in a private test repository on GitHub Actions. It created a release, the Docker image carried its id, and a Python app sent an event and an $exception with that $release_id.
• Not run: this workflow and the outage build. Both run only on master pushes or manual dispatch. The first master push after merge shows the resolved id, or the step error, in the job log.

Automatic notifications

• Publish to changelog?

Docs update

None. No doc under docs/ describes the release step.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Agent: Claude Code, Claude Opus 5.5

• Skills invoked: /authoring-ci-workflows, /gating-production-deploys, /depot-ci, /stacking-prs, /writing-code-comments, /writing-pr-descriptions, /reviewing-with-coderabbit.
• CodeRabbit CLI pass: skipped. The CLI was signed out, and the assignee chose to open the PR without a local pass.
• Duplicate search: gh pr list --state open --search "resolve-release OR resolve-error-tracking-release" found only feat(error-tracking): pass the release id into the django image #104420, which added the step this PR replaces.
• The same session built and released PostHog/resolve-release from the step in feat(error-tracking): pass the release id into the django image #104420.

🤖 Generated with Claude Code

[github-actions]

🤖 CI report

🚨 Trunk lane — universal lane

This PR is assigned to the universal lane. It cannot merge in parallel with other PRs, so it can take longer to merge. Ask dev-ex if you think this is wrong.

[greptile-apps]

The PR appears safe to merge with no actionable defect established in the changed workflows.

_{Reviews (1) · Last reviewed commit: "chore(ci): use the published resolve-rel..."}

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Important

Review skipped

We couldn't safely recover the incremental review. No full review was started, and the last reviewed checkpoint was preserved. Retry later, or explicitly request a full review by commenting @coderabbitai full review.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: PostHog/posthog/.coderabbit.yaml

Review profile: QUIET

Plan: Enterprise

Run ID: c06784aa-25ce-4d65-a69d-3a62d33fc946

📥 Commits

Reviewing files that changed from the base of the PR and between c10d68f and 61e7291.

📒 Files selected for processing (4)

• .depot/actions/resolve-error-tracking-release/action.yml
• .depot/workflows/actions-outage-image-build.yml
• .github/actions/resolve-error-tracking-release/action.yml
• .github/workflows/container-images-cd.yml

💤 Files with no reviewable changes (2)

• .depot/actions/resolve-error-tracking-release/action.yml
• .github/actions/resolve-error-tracking-release/action.yml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Walkthrough

Walkthrough

Both image workflows now use the pinned PostHog/resolve-release action. The outage image workflow omits the release version; the container image workflow retains its SHA-based release version. Both repository-local composite action definitions were removed.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 61e72

The image builds retain release resolution, with no identified regression that needs to be fixed before merging.

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description is complete and stand-alone. It explains the problem, changes, testing status, documentation status, and agent context. It does not include the required before-and-after Mermaid flowch…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[trunk-io]

😎 Stack merged successfully - details.

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-09-23 12:42 UTC	Run
prod-us	✅ Deployed	2026-09-23 12:53 UTC	Run
prod-eu	✅ Deployed	2026-09-23 12:55 UTC	Run