Repository navigation
feat(error-tracking): describe release linking for Python, Ruby and PHP - #1399
Merged
Merged
Conversation
The error-tracking flow now links each production deploy to a release on Python, Ruby and PHP (context-mill link-releases task). The linear-fallback prompt installs the error-tracking-link-releases skill on those platforms, and the intro, learn deck and command description name release linking. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a Context Mill branch:
Add Results will be posted here when complete. |
hpouillot
approved these changes
Sep 30, 2026
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.
Pull requests — release linking for Python, Ruby and PHP spans three repos:
error-tracking-link-releasesskill and thelink-releasesflow taskProblem
wizard error-trackingtreats Python, Ruby and PHP as "nothing to upload", so their exceptions never name the release they came from. PostHog now links releases for these SDKs throughPOSTHOG_RELEASE_ID, set by the production deploy (docs).Changes
The behavior lives in context-mill (PostHog/context-mill#416): the
error-tracking-link-releasesskill and alink-releasestask that the flow's seed queues for Python, Ruby and PHP server apps. The task wires the release into the production deploy only, and local runs stay unchanged. The wizard needs no new runner code. This PR aligns the wizard-side copy and the linear fallback:--sequence=linearprompt installs the matchingerror-tracking-link-releasesvariant on Python, Ruby and PHP.e2e.jsonsummary lists the release-linking step.How it was tested
pnpm typecheck, and theprograms(729),cli(149) and focused TUI/router vitest suites.pnpm build:ci, then headlesswizard error-tracking --ci --local-context-millagainst the three workbench fixtures (feat(error-tracking): add release-linking fixtures for Python, Ruby and PHP wizard-workbench#4266), with the context-mill dev server serving feat(error-tracking): link Python, Ruby and PHP deploys to releases context-mill#416. All three runs exit 0 and queuelink-releaseswith the right variant. The runtime checks and their results are in feat(error-tracking): link Python, Ruby and PHP deploys to releases context-mill#416.🤖 Generated with Claude Code