fix load posthogkey issue

[CarmenDou]

Fix missing POSTHOG_API_KEY in npm publish step

Adds POSTHOG_API_KEY from secrets to the env block of the npm publish step in publish.yml. Without this, the key was unavailable at publish time, causing PostHog initialization to fail.

^{Macroscope summarized c2e9e49.}

Summary by CodeRabbit

No user-facing changes in this release. This update modifies internal build and deployment processes only.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f788b0ac-d33c-4bab-b50f-449a49b93536

📥 Commits

Reviewing files that changed from the base of the PR and between d907c71 and c2e9e49.

📒 Files selected for processing (1)

• .github/workflows/publish.yml

---

Walkthrough

A GitHub Actions workflow configuration file receives an incremental update where the POSTHOG_API_KEY secret is injected as an environment variable into the npm publish step, supplementing its existing presence in the npm run build step.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/publish.yml	Added POSTHOG_API_KEY environment variable injection from secrets to the npm publish step.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• InsForge/CLI PR #39: Both PRs inject the POSTHOG_API_KEY secret into the publish workflow, with this PR adding it to the npm publish step.

Suggested reviewers

• tonychang04

Poem

🐰 A carrot for telemetry, so keen,
The publish step now shares what's been seen,
Keys aligned across the workflow flow,
Analytics whispers, everywhere they go! 📊✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix load posthogkey issue' is directly related to the changeset, which adds POSTHOG_API_KEY to the npm publish workflow step to resolve a PostHog key loading problem.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/load-posthogkey-issue

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[tonychang04]

LGTM — adds the missing POSTHOG_API_KEY env to the publish step so the key is available during build.