zeekay
26a9531f7b
# Conflicts: # .github/workflows/check-insights-major-version.yml # .github/workflows/check-posthog-major-version.yml # .github/workflows/ci-security.yaml # .github/workflows/validate-versioning.yml # AGENTS.md # AGENTS.md~upstream_main # packages/ai/src/otel/capture.ts # packages/ai/src/otel/mappers/aiSdk.ts # packages/ai/src/otel/mappers/index.ts # packages/ai/src/otel/types.ts # packages/core/src/__tests__/posthog.init.spec.ts # packages/react-native/src/PostHogProvider.tsx # packages/react/src/context/PostHogContext.ts # packages/react/src/context/PostHogProvider.tsx # tooling/eslint-plugin-insights/no-unsafe-web-global.js
1.1 KiB
Releases
Releases are managed with changeset, you can find more information on the changeset repository.
Before submitting a PR, create a changeset by running:
pnpm changeset
CLI will prompt questions about the changes you've made and will generate a changeset file for you.
When a PR containing a changeset is merged to main, the release workflow will automatically:
- Bump versions based on changesets
- Commit version updates directly to main
- Publish packages to npm
- Create GitHub releases
All of this happens automatically when the PR is merged - no intermediate PRs needed!
for @hanzo/insights browser sdk
When we run post-merge actions for the browser SDK we publish to NPM
But then we automagically open a PR against the main Insights repo. We don't update the CDN with the new version until that PR merges. So if it fails you can end up with html snippet users on version N and npm install on version N+1
Insightsgers can join the #alerts-@hanzo/insights channel in slack which gets notified when those PRs fail