ci: chart impit's own npm/PyPI release history on PR comments

[barjin]

Adds a workflow that benchmarks the last 5 npm and PyPI releases of impit against each other and comments a throughput chart on the PR, without committing the chart to the repo.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UnwET4Qxx14A9FG28Xniqx

---

Generated by Claude Code

[barjin]

The comment job is gated by on: pull_request (not pull_request_target) but uses secrets.APIFY_SERVICE_ACCOUNT_GITHUB_TOKEN; since pull_request runs the workflow definition from the PR's own head ref, and this workflow's paths filter includes itself (.github/workflows/version-benchmark.yaml), any PR editing that file controls the steps that see the token, independent of the ref: master checkout used inside those steps. Scale is otherwise proportional to the change (new CI workflow + supporting scripts, no library API changes).

---

Generated by Claude Code

[apify-service-account]

impit version comparison

Median throughput of the last 5 npm and PyPI releases of impit.

[barjin]

Good catch. Fixed in 6640681: split the comment-posting job into its own version-benchmark-comment.yaml, triggered by workflow_run instead of a second job on pull_request. workflow_run always runs the copy of the file from master, so a PR editing the workflow can no longer control what the job holding the push token does.

Note this means the comment workflow won't actually fire until it exists on master (a workflow_run listener is only registered from the default branch's copy) — so this PR itself won't get a fresh comment from the fixed path until merged; the earlier comment here was posted by the pre-fix version.

---

Generated by Claude Code