Skip to content

fix(ci): explicitly dispatch publish.yml after creating release#10

Merged
Gdewilde merged 2 commits intomainfrom
fix/auto-publish-on-release
Apr 26, 2026
Merged

fix(ci): explicitly dispatch publish.yml after creating release#10
Gdewilde merged 2 commits intomainfrom
fix/auto-publish-on-release

Conversation

@Gdewilde
Copy link
Copy Markdown
Contributor

Summary

  • v0.7.0 and v0.8.0 were tagged + released on GitHub but never landed on npm. Root cause: GitHub suppresses workflow triggers for events created by `GITHUB_TOKEN` (anti-recursion safeguard), so the `release: published` event from `gh release create` silently failed to fire `publish.yml`.
  • After creating the release, explicitly invoke `publish.yml` via `gh workflow run --ref v`. `workflow_dispatch` via the API is not subject to the same suppression.
  • Adds the `actions: write` permission needed to dispatch the downstream workflow.

v0.7.0 and v0.8.0 have already been backfilled to npm manually via `gh workflow run publish.yml --ref v0.7.0` / `v0.8.0`.

Test plan

  • Merge, then bump `package.json` version on a follow-up PR and confirm the release + publish runs both fire end-to-end without manual intervention.

🤖 Generated with Claude Code

Gdewilde and others added 2 commits April 26, 2026 19:31
Keep the library PII-free by default — country_code now requires
captureCountry: true, matching the existing captureIp opt-in. Coarse
country is low-risk but still user-derived, so it shouldn't leak into
events without an explicit choice.

Adds a README section explaining how to feed the resulting events into
Peec.ai's crawl-insights CSV via a PostHog SQL export, replacing the
Vercel Log Drain → Axiom pipeline their docs assume.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
GitHub suppresses workflow triggers for events created by GITHUB_TOKEN, so
the `release: published` event from `gh release create` was silently failing
to fire publish.yml. v0.7.0 and v0.8.0 were tagged + released on GitHub but
never reached npm as a result (backfilled manually).

Trigger publish.yml explicitly via `gh workflow run --ref v<version>` after
creating the release. workflow_dispatch via the API is not subject to the
same anti-recursion suppression.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Gdewilde Gdewilde merged commit b388803 into main Apr 26, 2026
3 checks passed
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.

1 participant