Skip to content

feat(error-tracking): add release-linking fixtures for Python, Ruby and PHP - #4266

Merged
ablaszkiewicz merged 1 commit into
mainfrom
feat/error-tracking-link-releases
Oct 2, 2026
Merged

ablaszkiewicz merged 1 commit into
mainfrom
feat/error-tracking-link-releases

Conversation

@ablaszkiewicz

@ablaszkiewicz ablaszkiewicz commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Pull requests — release linking for Python, Ruby and PHP spans three repos:

  1. feat(error-tracking): link Python, Ruby and PHP deploys to releases context-mill#416: the error-tracking-link-releases skill and the link-releases flow task
  2. feat(error-tracking): describe release linking for Python, Ruby and PHP wizard#1399: wizard copy and the linear-fallback prompt
  3. 👉 feat(error-tracking): add release-linking fixtures for Python, Ruby and PHP #4266: the Python, Ruby and PHP test apps (this PR)

Problem

The error-tracking fixtures cover source-map upload only. Python, Ruby and PHP apps now get release linking in the production deploy (PostHog/context-mill#416), which needs apps with real deploy pipelines to run against.

Changes

Three apps under apps/error-tracking/, one per language, each with a different deploy path:

App Stack Deploy path
cicd-github-actions-docker-python-flask Flask + gunicorn, no PostHog GitHub Actions builds a multi-stage image, pushes to GHCR, docker run over SSH; ci.yml tests pull requests
cicd-gitlab-ruby-sinatra Sinatra + Puma, PostHog on posthog-ruby 3.20.0 GitLab deploy job on ruby:3.3-slim SSHes in and restarts a systemd unit with an EnvironmentFile; the test job covers merge requests
cicd-github-actions-docker-php-laravel Laravel 12 on php:8.4-fpm-alpine, no PostHog GitHub Actions pushes the image and rolls out a compose stack over SSH; the entrypoint runs config:cache and the pool sets clear_env = yes
  • The expectations for each app are in apps/error-tracking/README.md. The app READMEs describe only the project, because the agent reads them and would take expectations as instructions.
  • The Laravel app keeps its storage/**/.gitignore and bootstrap/cache/.gitignore placeholders, force-added past the root **/storage/ rule, so a clean checkout builds and boots.
  • The Flask app's local entry point is bin/dev, because the root .gitignore excludes Makefile.

How it was tested

Headless wizard error-tracking --ci --local-context-mill runs against copies of each app, followed by runtime checks that deploy the result the way its pipeline does. All three pass; the results table is in PostHog/context-mill#416. The Laravel app also builds and boots from a clean git archive of this branch.

🤖 Generated with Claude Code

…nd PHP

Three error-tracking apps with production deploy pipelines, one per language:
- cicd-github-actions-docker-python-flask: Flask, GitHub Actions, Docker image
  rolled out over SSH with docker run
- cicd-gitlab-ruby-sinatra: Sinatra on an older posthog-ruby, GitLab CI deploy
  over SSH to a systemd unit with an EnvironmentFile
- cicd-github-actions-docker-php-laravel: Laravel on php-fpm with clear_env,
  config:cache at start, compose rollout over SSH

The expectations live in apps/error-tracking/README.md, outside the app
directories the wizard agent reads.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ablaszkiewicz
ablaszkiewicz merged commit df0c69f into main Oct 2, 2026
11 checks passed
@ablaszkiewicz
ablaszkiewicz deleted the feat/error-tracking-link-releases branch October 2, 2026 09:40
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.

2 participants